From: Antoine Kalmbach <ane@iki.fi>
To: Sam James <sam@gentoo.org>
Cc: emacs-devel@gnu.org, Philip Kaluderdic <philipk@posteo.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Juri Linkov <juri@linkov.net>
Subject: Re: Supporting git-send-email/hg email in VC
Date: Thu, 25 Aug 2022 11:36:55 +0300 [thread overview]
Message-ID: <84y1vcn2hk.fsf@iki.fi> (raw)
In-Reply-To: <3E4E0239-22AA-4AB9-A092-3DC5404983C0@gentoo.org>
It seems I wrote a bunch of replies off-list. Oops. Anyway, a summary of
what I think are the conclusions.
First, by relying only on git-format-patch to produce the emailsin the
Git backend we should not be omitting any nuance that git-send-email
has. Thus if we take the .patch file(s) directly and then open those in
the MUA of the user, we won't do anything drastically different from
git-email. The patches will by default be inline, though I suppose users
could customize these to become attachments, but these won't obviously
work with `git am`.
Sam James <sam@gentoo.org> writes:
> Often, people are told to defer to git send-email because it definitely
> does Things Right, but I haven't looked into the things it takes
> care to do correctly. It might be easy for Emacs to do those.
I will keep digging into this until I can be relatively confident about
the differences. Looking at the source code and manuals it seems to me
that git-format-patch is doing the heavy lifting and git-send-email is
just a MUA on top of that. I mean, git-send-email accepts .patch files
by git-format-patch as an argument, so it really appears just to be a
MUA.
But I need to be absolutely sure before proceeding.
--
Antoine Kalmbach
next prev parent reply other threads:[~2022-08-25 8:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 11:56 Supporting git-send-email/hg email in VC Antoine Kalmbach
2022-08-24 14:43 ` Akib Azmain Turja
2022-08-24 15:11 ` Philip Kaludercic
2022-08-24 17:06 ` Stefan Monnier
2022-08-24 17:44 ` Juri Linkov
2022-08-24 21:31 ` Sam James
2022-08-25 8:36 ` Antoine Kalmbach [this message]
2022-08-25 14:47 ` Sean Whitton
2022-08-25 15:52 ` Philip Kaludercic
2022-08-25 22:04 ` Sean Whitton
2022-08-25 17:34 ` Stefan Monnier
2022-08-25 18:04 ` Philip Kaludercic
2022-08-26 7:14 ` Antoine Kalmbach
2022-08-26 7:15 ` Antoine Kalmbach
2022-08-26 3:35 ` Richard Stallman
2022-08-26 7:12 ` Antoine Kalmbach
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=84y1vcn2hk.fsf@iki.fi \
--to=ane@iki.fi \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=sam@gentoo.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).