From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: master 47070ed 6/6: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
Date: Sun, 16 May 2021 00:37:21 -0400 [thread overview]
Message-ID: <E1li8Wn-0006xm-8D@fencepost.gnu.org> (raw)
In-Reply-To: <83im3lztno.fsf@gnu.org> (message from Eli Zaretskii on Fri, 14 May 2021 10:00:44 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Do you remember the question it asked? Was it something like the
> below?
> # Please enter a commit message to explain why this merge is necessary,
> # especially if it merges an updated upstream into a topic branch.
> #
> # Lines starting with '#' will be ignored and an empty message aborts
> # the commit.
I think so.
> If so, this is not really a question you need to answer. The line
> above it is the merge-commit log message Git prepares for you (it
> probably said something like "Merge branch 'master' of
> git.sv.gnu.org:/srv/git/emacs"),
It was not obvious to me that the text above constitutes a possible answer.
I thought it was simply information being shown to me.
so basically all you need to do is
> "C-c C-c" to let Git use that standard message and proceed with the
> merge.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-05-16 4:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210512030946.27770.7288@vcs0.savannah.gnu.org>
[not found] ` <20210512030949.65CD421128@vcs0.savannah.gnu.org>
2021-05-12 8:16 ` master 47070ed 6/6: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Robert Pluim
2021-05-12 12:50 ` Eli Zaretskii
2021-05-13 4:53 ` Richard Stallman
2021-05-13 6:38 ` Eli Zaretskii
2021-05-14 5:23 ` Richard Stallman
2021-05-14 7:00 ` Eli Zaretskii
2021-05-14 13:45 ` Stefan Monnier
2021-05-14 14:49 ` Andreas Schwab
2021-05-16 4:37 ` Richard Stallman [this message]
[not found] ` <20210512030948.6448F21128@vcs0.savannah.gnu.org>
2021-05-12 12:17 ` master 42596bd 2/6: Little improvements in rmail.el. Recognize encryped override headers Lars Ingebrigtsen
2021-05-12 13:12 ` Eli Zaretskii
2021-05-12 13:16 ` Lars Ingebrigtsen
2021-05-12 13:20 ` Eli Zaretskii
2021-05-12 15:14 ` Stefan Monnier
2021-05-12 15:45 ` Eli Zaretskii
2021-05-12 15:47 ` Lars Ingebrigtsen
2021-05-12 15:59 ` Eli Zaretskii
2021-05-12 15:54 ` Robert Pluim
2021-05-12 14:03 ` Gregory Heytings
2021-05-12 14:17 ` Gregory Heytings
2021-05-13 4:52 ` Richard Stallman
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=E1li8Wn-0006xm-8D@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/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).