all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 20325@debbugs.gnu.org, michael.albinus@gmx.de, dgutov@yandex.ru
Subject: bug#20325: convert "fixes:debbugs:123" in log to (Bug#123) in ChangeLog
Date: Sun, 19 Apr 2015 17:23:31 +0300	[thread overview]
Message-ID: <831tjg6vto.fsf@gnu.org> (raw)
In-Reply-To: <553319F6.2050404@cs.ucla.edu>

> Date: Sat, 18 Apr 2015 19:59:02 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: michael.albinus@gmx.de, 20325@debbugs.gnu.org
> 
> Eli Zaretskii wrote:
> > For some value of "we".  CONTRIBUTE still requires to use
> > "Fixes: bug#NNNN", and that's what I've switched to once those
> > requirements were written.  Which was already a change from the
> > previous procedure, which preferred simply "Bug#NNNN".
> >
> > I wish you guys settle on something once and for all, never mind what,
> 
> "you guys"?  I thought you were one of us!  :-)

Not in this bikeshedding, sorry.

> I did not choose the "Fixes: bug#NNNN" syntax.  I vaguely recall it came from an 
> offhand remark in one of Stefan's emails a few months ago and that it migrated 
> into CONTRIBUTE when Stephen Leake attempted to summarize that discussion, but 
> possibly it was a typo in Stefan's message and anyway I expect he doesn't much 
> care what the format is.
> 
>  From the earlier discussion in this thread it appears that the "Fixes: 
> debbugs:NNNN" syntax is an artifact of the Bzr-to-Git conversion that now causes 
> more confusion than it's worth.  To try to lessen this I installed the attached 
> patches (the third one is mechanical; it's the result of 'make change-history').

Thanks.  Let's hope this one holds one a bit longer than its
predecessors.





  reply	other threads:[~2015-04-19 14:23 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 [this message]
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=831tjg6vto.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20325@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eggert@cs.ucla.edu \
    --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.