From: Darren Hoo <darren.hoo@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: The fixes-bug field
Date: Fri, 17 Jan 2014 02:38:48 +0800 [thread overview]
Message-ID: <m24n53ixfr.fsf@gmail.com> (raw)
In-Reply-To: hir48724og.fsf@fencepost.gnu.org
Glenn Morris <rgm@gnu.org> writes:
> Eli Zaretskii wrote:
>
>> I think we should decide on how to store this info and how to report
>> the fixed bugs once we switch to git, before we decide on how to
>> convert this data from bzr, and whether or not this justifies a new
>> conversion from scratch rather than reuse of the existing mirror.
>
> Absolutely.
>
> I also suggest that any conversion standardize the format of the entries.
> At present you find examples of both
>
> http://debbugs.gnu.org/16462
>
> and
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16462
>
> Both point to the same place, but I think the former format is better.
What benefit do we get by using bzr fixes bug over mentioning it in the
commit log like (Bug#16462)? I can see some of them in the ChangeLogs.
I like (Bug#16462) better because it also appears in the ChangeLog.
and since the Bug Id is universal, using full url is somewhat redundant.
As a regular user it is easier for me to just go through the ChangeLog file
to check whether a certain bug I care about is fixed in Emacs releases.
next prev parent reply other threads:[~2014-01-16 18:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 14:13 The fixes-bug field Eric S. Raymond
2014-01-16 16:13 ` Stefan Monnier
2014-01-16 16:30 ` Eric S. Raymond
2014-01-16 16:55 ` Eli Zaretskii
2014-01-16 17:54 ` Glenn Morris
2014-01-16 18:09 ` Eric S. Raymond
2014-01-16 18:38 ` Darren Hoo [this message]
2014-01-16 19:32 ` Stefan Monnier
2014-01-16 20:06 ` Glenn Morris
2014-01-16 21:30 ` Eli Zaretskii
2014-01-16 21:24 ` Eli Zaretskii
2014-01-16 18:55 ` Paul Eggert
2014-01-16 19:13 ` Glenn Morris
2014-01-16 20:25 ` Paul Eggert
2014-01-16 18:08 ` Eric S. Raymond
2014-01-16 18:36 ` Eli Zaretskii
2014-01-16 20:04 ` Eric S. Raymond
2014-01-16 21:29 ` Eli Zaretskii
2014-01-16 21:47 ` Eric S. Raymond
2014-01-17 7:32 ` Eli Zaretskii
2014-01-17 7:58 ` Paul Eggert
2014-01-17 8:04 ` Jarek Czekalski
2014-01-17 9:21 ` Yuri Khan
2014-01-17 14:31 ` Stefan Monnier
2014-01-17 15:57 ` Lars Ingebrigtsen
2014-01-17 16:12 ` Stefan Monnier
2014-01-17 17:20 ` Lars Ingebrigtsen
2014-01-18 9:19 ` Jarek Czekalski
2014-01-18 16:02 ` Lars Ingebrigtsen
2014-01-17 13:16 ` Eric S. Raymond
2014-01-17 13:55 ` Eli Zaretskii
2014-01-17 14:26 ` Stefan Monnier
2014-01-16 17:00 ` Glenn Morris
2014-01-16 17:22 ` Achim Gratz
2014-01-16 17:57 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 14:15 Eric S. Raymond
2014-01-16 17:11 ` Eli Zaretskii
2014-01-17 20:29 ` Eric S. Raymond
2014-01-18 7:51 ` 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=m24n53ixfr.fsf@gmail.com \
--to=darren.hoo@gmail.com \
--cc=emacs-devel@gnu.org \
/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).