From: Dmitry Gutov <dgutov@yandex.ru>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 20325@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#20325: convert "fixes:debbugs:123" in log to (Bug#123) in ChangeLog
Date: Fri, 17 Apr 2015 19:30:11 +0300 [thread overview]
Message-ID: <55313513.4070704@yandex.ru> (raw)
In-Reply-To: <33237A23-C3B2-40FD-9BC2-B43FEE51A2E7@swipnet.se>
On 04/17/2015 07:20 PM, Jan D. wrote:
> What about a few years from now when we switch to something other than debbugs?
That's exactly the situation where having used debbugs:1234 until that
point will show its benefits.
> Why hardcode a specific bug reporting tool as the recommendation?
Will all bugs be migrated to the new bug reporting tool? Will they keep
their identifiers?
Unless you're 100% sure about that, explicitly documenting which bug
tracker the bugs are reported in is a useful information.
next prev parent reply other threads:[~2015-04-17 16:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 6:01 bug#20325: convert "fixes:debbugs:123" in log to (Bug#123) in ChangeLog Glenn Morris
2015-04-17 6:46 ` Paul Eggert
2015-04-17 11:25 ` Dmitry Gutov
2015-04-17 15:19 ` Paul Eggert
2015-04-17 15:32 ` Dmitry Gutov
2015-04-17 15:56 ` Paul Eggert
2015-04-17 16:02 ` Dmitry Gutov
2015-04-17 16:25 ` Jan D.
2015-04-17 16:20 ` Jan D.
2015-04-17 16:30 ` Dmitry Gutov [this message]
2015-04-17 17:06 ` Jan D.
2015-04-17 17:15 ` Dmitry Gutov
2015-04-18 7:46 ` Jan D.
2015-04-18 8:08 ` Eli Zaretskii
2015-04-17 21:45 ` Michael Albinus
2015-04-17 21:48 ` Dmitry Gutov
2015-04-17 22:02 ` Michael Albinus
2015-04-17 22:44 ` Dmitry Gutov
2015-04-18 1:02 ` Paul Eggert
2015-04-18 6:28 ` Michael Albinus
2015-04-18 7:25 ` Eli Zaretskii
2015-04-18 9:25 ` Ivan Shmakov
2015-04-18 9:46 ` Eli Zaretskii
2015-04-18 7:14 ` Eli Zaretskii
2015-04-19 2:59 ` Paul Eggert
2015-04-19 14:23 ` Eli Zaretskii
2015-04-20 21:54 ` Glenn Morris
2015-04-21 1:17 ` Stefan Monnier
2015-04-21 3:41 ` Paul Eggert
2015-04-21 14:48 ` Stefan Monnier
2015-04-24 18:35 ` Glenn Morris
2015-04-24 18:55 ` Paul Eggert
2015-04-24 19:13 ` Glenn Morris
2015-04-24 19:19 ` Glenn Morris
2015-04-24 20:27 ` Stefan Monnier
2015-04-24 21:41 ` Paul Eggert
2015-04-25 7:17 ` Jan D.
2015-04-25 14:47 ` Stefan Monnier
2015-04-27 18:34 ` Glenn Morris
2015-04-21 14:49 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55313513.4070704@yandex.ru \
--to=dgutov@yandex.ru \
--cc=20325@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jan.h.d@swipnet.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).