From: Paul Eggert <eggert@cs.ucla.edu>
To: Dmitry Gutov <dgutov@yandex.ru>,
Michael Albinus <michael.albinus@gmx.de>
Cc: 20325@debbugs.gnu.org
Subject: bug#20325: convert "fixes:debbugs:123" in log to (Bug#123) in ChangeLog
Date: Fri, 17 Apr 2015 18:02:51 -0700 [thread overview]
Message-ID: <5531AD3B.8080705@cs.ucla.edu> (raw)
In-Reply-To: <55318CEB.2010904@yandex.ru>
Dmitry Gutov wrote:
> We've used the debbugs:1234 format in commit messages for a while now.
We've used several formats. "Fixes: debbugs:NNNN" is designed for Bzr I think,
"(Bug#NNNN)" is the more-traditional form, and CONTRIBUTE currently recommends a
third format "Fixes: bug#NNNN".
In practice, about as many commits these days use the Bzr-ish format as use the
more-traditional form (see (*) below). I don't know why we're still using a
Bzr-ish format (is it just inertia?), and I don't know why CONTRIBUTE disagrees
with both the commonly-used formats.
Since we're not using Bzr any more, how about if we change CONTRIBUTE to suggest
the more-traditional "(Bug#NNNN)" form? Any new technology that replaces
debbugs would have to handle the same bug numbers as before, I expect.
(*) I surveyed the 2213 commits since November 1 (this is a bit before the Git
transition), i.e., all commits from d87931d249a4c7f15d4c1178c6ce396ab18ce1f6
through 35be45bbc9ac525bb2bc3e20b0fa27c1ceee0c15, and found the following number
of instances of each format:
count example of the style
262 Fixes: debbugs:20357
172 (Bug#20011)
49 (bug#20276)
24 Fixes: bug#20338
8 Fix bug#19891
6 Fixes: Bug#20338
5 Fixes: 18757
5 Fixes Bug#15880.
2 Fixes: debbugs:19387 debbugs:19405
1 Fixes: debbugs:19134.
1 Fixes: big#19528
1 Fixes (bug#17284).
1 Fix Bug#20249
next prev parent reply other threads:[~2015-04-18 1:02 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5531AD3B.8080705@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=20325@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=michael.albinus@gmx.de \
/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.