From: Eli Zaretskii <eliz@gnu.org>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org, tsdh@gnu.org
Subject: Re: master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk
Date: Tue, 02 Feb 2021 17:23:51 +0200 [thread overview]
Message-ID: <83h7mu5w8o.fsf@gnu.org> (raw)
In-Reply-To: <20210202090632.GA26805@tuxteam.de> (tomas@tuxteam.de)
> Date: Tue, 2 Feb 2021 10:06:32 +0100
> From: <tomas@tuxteam.de>
> Cc: emacs-devel@gnu.org
>
> The nice thing about git is that it makes those things explicit [1].
Careful: there are those (including yours truly) who think that this
is a terrible misfeature, which only benefits people with too much
time on their hands and the wish to understand the innards of Git. A
VCS should do its job without asking me to understand too much about
its mechanics. If I want to know how it works, I will then go ahead
and read on it, or even (gasp!) look at its sources.
next prev parent reply other threads:[~2021-02-02 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210131223952.429.10439@vcs0.savannah.gnu.org>
[not found] ` <20210131223954.A429420DF3@vcs0.savannah.gnu.org>
2021-02-02 0:44 ` master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk Katsumi Yamaoka
2021-02-02 2:58 ` Stefan Monnier
2021-02-02 5:41 ` Richard Stallman
2021-02-02 6:38 ` Tassilo Horn
2021-02-02 9:06 ` tomas
2021-02-02 15:23 ` Eli Zaretskii [this message]
2021-02-02 16:01 ` tomas
2021-02-02 16:21 ` Eli Zaretskii
2021-02-02 16:34 ` git things [was: master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk] tomas
2021-02-03 5:51 ` master 11abc4a: Merge remote-tracking branch 'origin/scratch/lexical-gnus' into trunk Richard Stallman
2021-02-02 8:16 ` Andreas Schwab
2021-02-02 15:06 ` Eli Zaretskii
2021-02-03 5:52 ` Richard Stallman
2021-02-03 14:32 ` Eli Zaretskii
2021-02-04 5:47 ` Richard Stallman
2021-02-02 9:05 ` Lars Ingebrigtsen
2021-02-02 14:43 ` Stefan Monnier
2021-02-02 14:53 ` Lars Ingebrigtsen
2021-02-02 22:12 ` Katsumi Yamaoka
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=83h7mu5w8o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
--cc=tsdh@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).