all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 20325@debbugs.gnu.org,  dgutov@yandex.ru
Subject: bug#20325: convert "fixes:debbugs:123" in log to (Bug#123) in ChangeLog
Date: Sat, 18 Apr 2015 09:25:30 +0000	[thread overview]
Message-ID: <877ft9rdo5.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <83a8y599u7.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Apr 2015 10:25:36 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>> From: Paul Eggert <eggert@cs.ucla.edu>

 >> "Fixes: debbugs:NNNN" is designed for Bzr I think,

 > Bzr didn't have this in the log messages, it had this as meta-data.
 > Conversion to Git moved this into the commit log, since AFAIK Git
 > doesn't have such an attribute in its meta-data.

	I guess the above means there’s no valid reason to stick to this
	format any longer?

 >> count  example of the style
 >> 262    Fixes: debbugs:20357
 >> 172    (Bug#20011)
 >>  49    (bug#20276)

	I believe these two are essentially the same format – subject to
	the usual capitalization rules.  Consider, e. g.:

	* lisp/foo.el (foo-bar): Do not call qux.  (Bug#54321)
	* lisp/baz.el (baz-mode): Let-bind foo-1 to nil (bug#53210) and
	call bar.

	FWIW, I’d prefer to just stick with the (bug#) markers for
	commit messages, and let them propagate as is to the ChangeLog
	when one’s generated.

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A





  reply	other threads:[~2015-04-18  9:25 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 [this message]
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=877ft9rdo5.fsf_-_@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=20325@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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.