From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 20325@debbugs.gnu.org
Subject: bug#20325: convert "fixes:debbugs:123" in log to (Bug#123) in ChangeLog
Date: Sat, 25 Apr 2015 10:47:23 -0400 [thread overview]
Message-ID: <jwvvbgkclqu.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <553AB88C.9050901@cs.ucla.edu> (Paul Eggert's message of "Fri, 24 Apr 2015 14:41:32 -0700")
>> I think we shouldn't look at recent commits but at all commits in
>> the repository, since we want to reduce variation overall.
> Then the counts are closer. If one looks at the current 1,021,440-line
> output of 'git log', 3515 lines match the regular expression
> 'bug#[0-9][0-9][0-9]' and 2906 lines match 'debbugs:[0-9][0-9][0-9]',
> ignoring case for both searches.
No need to count. The convention was very clear and followed fairly
consistently: use (bug#NNN) in the ChangeLog, which gets turned into
"Fixes: debbugs:NNNN" in the *VC-Log* buffer (and was then turned into
a "--fixes debbugs:NNNN" argument to bzr which finally turned it into
a "Fixes: URL" message in the "bzr log" output).
Some/many (Bug#NNN) ended up in the commit log, and IIUC Eric's
conversion to Git turned Bzr's internal "Fixes" into "Fixes: debbugs:NNNN".
So, AFAIK, in terms of "pseudo-header syntax", the only thing we've used
consistently is "Fixes: debbugs:NNNN".
Stefan
next prev parent reply other threads:[~2015-04-25 14:47 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvvbgkclqu.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=20325@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.