all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
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: Mon, 20 Apr 2015 17:54:52 -0400	[thread overview]
Message-ID: <ttmw22wjmb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5530AC62.2010209@cs.ucla.edu> (Paul Eggert's message of "Thu, 16 Apr 2015 23:46:58 -0700")

Paul Eggert wrote:

> Wouldn't it be better to use the same format in commit messages and in
> ChangeLog.2?  That will be less confusing for everybody.

I didn't have a problem with it (different formats), and judging from
the logs not many other people seemed to either. For a long time, Emacs
has provided the tools to seamlessly create a commit log in the right
format from a ChangeLog. I'd have preferred to see gitlog-to-changelog
get the small update needed to go in the other direction, rather than
having the Emacs convention changed (soon after we just had a brand-new
repo created using the "fixes: debbugs:123" convention throughout). (But
since it's already a fait accompli this is just me bitching rather than
asking you to change it back.)

Presumably this means the solution to http://debbugs.gnu.org/20324
will be to modify gitlog-to-changelog to recognize "(tiny change)".
Emacs will still need to be modified to pass (tiny change) through to
the VC log though.





  parent reply	other threads:[~2015-04-20 21:54 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 [this message]
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=ttmw22wjmb.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --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.