From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, Boruch Baum <boruch_baum@gmx.com>, 47784@debbugs.gnu.org
Subject: bug#47784: 27.2: ses-header-row [PATCH INCLUDED]
Date: Thu, 06 May 2021 10:10:44 +0200 [thread overview]
Message-ID: <877dkc8epn.fsf@gmail.com> (raw)
In-Reply-To: <83bl9pezfo.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 May 2021 22:46:35 +0300")
>>>>> On Wed, 05 May 2021 22:46:35 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Wed, 5 May 2021 15:40:46 -0400
>> From: Boruch Baum <boruch_baum@gmx.com>
>> Cc: larsi@gnus.org, 47784@debbugs.gnu.org
>>
>> > "C-x 4 a" will automatically produce a ChangeLog-formatted buffer,
>> > from which you could copy the log message when you commit.
>>
>> Is this some new and 'backward-incompatible' behavior?
Eli> It's new, but not backward-incompatible, I think. AFAIR it only
Eli> happens when the buffer visits a versioned file.
From NEWS.27:
*** New command 'log-edit-generate-changelog-from-diff', bound to 'C-c C-w'.
This generates ChangeLog entries from the VC fileset diff.
*** Recording ChangeLog entries doesn't require an actual file.
If a ChangeLog file doesn't exist, and if the new user option
'add-log-dont-create-changelog-file' is non-nil (which is the
default), commands such as 'C-x 4 a' will add log entries to a
suitable named temporary buffer. (An existing ChangeLog file will
still be used if it exists.) Set the user option to nil to get the
previous behavior of always creating a buffer that visits a ChangeLog
file.
If you use vc, then 'vc-checkin' will copy the log message from the
ChangeLog to the commit log edit buffer for you (and that I think itʼs
been doing for a long time).
Robert
--
next prev parent reply other threads:[~2021-05-06 8:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 3:31 bug#47784: 27.2: ses-header-row [PATCH INCLUDED] Boruch Baum
2021-04-17 19:30 ` Eli Zaretskii
2021-04-19 9:24 ` Boruch Baum
2021-04-19 13:03 ` Eli Zaretskii
2021-04-19 13:27 ` Boruch Baum
2021-04-21 0:02 ` Stefan Kangas
2021-04-21 9:23 ` Eli Zaretskii
2021-05-05 13:08 ` Lars Ingebrigtsen
2021-05-05 16:40 ` Boruch Baum
2021-05-05 19:15 ` Eli Zaretskii
2021-05-05 19:40 ` Boruch Baum
2021-05-05 19:46 ` Eli Zaretskii
2021-05-06 8:10 ` Robert Pluim [this message]
2021-05-06 11:05 ` Boruch Baum
2021-05-06 8:17 ` Lars Ingebrigtsen
2021-05-06 10:16 ` Boruch Baum
2021-05-07 11:14 ` Lars Ingebrigtsen
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=877dkc8epn.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=47784@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).