From: Glenn Morris <rgm@gnu.org>
To: ams@gnu.org
Cc: 12946@debbugs.gnu.org
Subject: bug#12946: 23.2; log-edit-insert-changelog not inserting a description line from ChangeLog file
Date: Tue, 20 Nov 2012 13:30:50 -0500 [thread overview]
Message-ID: <biehjocejp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1TasCx-0003uA-P8@fencepost.gnu.org> (Alfred M. Szmidt's message of "Tue, 20 Nov 2012 13:06:03 -0500")
Alfred M. Szmidt wrote:
> 2012-11-16 Alfred M. Szmidt <ams@gnu.org>
>
> This is a deccription line.
>
> * random-file: New file.
If you don't use a blank line between the two, you get
This is a description line.
* random-file: New file.
in the log buffer, which seems fine to me. You can easily kill all but
the first line if you don't want it.
http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs
says not to put blank lines between related entries (essentially, IMO).
(Maybe it should be updated for the practise of adding a leading summary.)
> * random-file: New file.
>
> What would be useful is that you got the description line inserted
> instead, with nothing following it. This is common practise when
> working with various distributed version control systems where the
> commit entry only contains a brief description of the change, and the
> ChangeLog contains the detailed information.
Really? I got the impression the trend was to generate ChangeLogs from
commit logs.
next prev parent reply other threads:[~2012-11-20 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 18:06 bug#12946: 23.2; log-edit-insert-changelog not inserting a description line from ChangeLog file Alfred M. Szmidt
2012-11-20 18:30 ` Glenn Morris [this message]
2012-11-20 18:53 ` Alfred M. Szmidt
2012-11-20 18:58 ` Glenn Morris
2012-11-20 20:27 ` Alfred M. Szmidt
2012-11-20 20:19 ` Stefan Monnier
2012-11-20 20:29 ` Alfred M. Szmidt
2012-11-20 20:46 ` Glenn Morris
2012-11-21 13:48 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=biehjocejp.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12946@debbugs.gnu.org \
--cc=ams@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).