unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 47784@debbugs.gnu.org
Subject: bug#47784: 27.2: ses-header-row [PATCH INCLUDED]
Date: Wed, 5 May 2021 15:40:46 -0400	[thread overview]
Message-ID: <20210505194046.c6oofhqfdwdqew4p@E15-2016.optimum.net> (raw)
In-Reply-To: <83czu5f0vu.fsf@gnu.org>

On 2021-05-05 22:15, Eli Zaretskii wrote:
> > Date: Wed, 5 May 2021 12:40:34 -0400
> > From: Boruch Baum <boruch_baum@gmx.com>
> > Cc: 47784@debbugs.gnu.org
> >
> > I use `C-x 4 a' a lot, but for Changelog files. How can it be used for
> > commit messages? Are you suggesting a temporary fake Changelog file?
>
> "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? In the past, I
remember it always creating a Changelog file...

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





  reply	other threads:[~2021-05-05 19:40 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 [this message]
2021-05-05 19:46         ` Eli Zaretskii
2021-05-06  8:10           ` Robert Pluim
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=20210505194046.c6oofhqfdwdqew4p@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=47784@debbugs.gnu.org \
    --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).