From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 63802@debbugs.gnu.org
Subject: [bug#63802] [mumi PATCH 1/3] client: Do not pass --add-header to git send-email.
Date: Sun, 04 Jun 2023 22:21:15 -0400 [thread overview]
Message-ID: <875y82ejj8.fsf@gmail.com> (raw)
In-Reply-To: <20230530121447.26236-1-arunisaac@systemreboot.net> (Arun Isaac's message of "Tue, 30 May 2023 13:14:45 +0100")
Hi Arun!
Arun Isaac <arunisaac@systemreboot.net> writes:
> git send-email accepts --add-header only when passed a git
> format-patch style revision list.
LGTM. The idea is that this is now handled by a configured git
'add-header-cmd' such as Guix' etc/teams.scm, correct?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-06-05 2:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:11 [bug#63802] [mumi PATCH 0/3] Use consolidated X-Debbugs-Cc header Arun Isaac
2023-05-30 12:14 ` [bug#63802] [mumi PATCH 1/3] client: Do not pass --add-header to git send-email Arun Isaac
2023-05-30 12:14 ` [bug#63802] [mumi PATCH 2/3] client: Add git-send-email-headers subcommand Arun Isaac
2023-06-05 2:31 ` Maxim Cournoyer
2023-06-08 17:09 ` Arun Isaac
2023-06-08 17:29 ` Arun Isaac
2023-05-30 12:14 ` [bug#63802] [mumi PATCH 3/3] client: Use mumi " Arun Isaac
2023-06-05 2:36 ` Maxim Cournoyer
2023-06-05 2:21 ` Maxim Cournoyer [this message]
2023-06-08 17:14 ` [bug#63802] [PATCH 1/3] client: Separate serialize-email-address into a function Arun Isaac
2023-06-08 17:14 ` [bug#63802] [PATCH 2/3] client: Add git-send-email-headers subcommand Arun Isaac
2023-07-16 3:39 ` [bug#63802] [mumi PATCH 0/3] Use consolidated X-Debbugs-Cc header Maxim Cournoyer
2023-07-17 22:14 ` Arun Isaac
2023-07-18 15:32 ` Maxim Cournoyer
2023-07-19 16:49 ` bug#63802: " Arun Isaac
2023-06-08 17:14 ` [bug#63802] [PATCH 3/3] client: Use mumi git-send-email-headers subcommand Arun Isaac
2023-07-16 4:01 ` [bug#63802] [mumi PATCH 0/3] Use consolidated X-Debbugs-Cc header Maxim Cournoyer
2023-07-17 22:14 ` Arun Isaac
2023-07-16 3:14 ` Maxim Cournoyer
2023-07-17 22:19 ` [bug#63802] [PATCH 1/3] client: Separate serialize-email-address into a procedure Arun Isaac
2023-07-17 22:19 ` [bug#63802] [PATCH 2/3] client: Add git-send-email-headers subcommand Arun Isaac
2023-07-17 22:19 ` [bug#63802] [PATCH 3/3] client: Use mumi " Arun Isaac
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y82ejj8.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=63802@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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/guix.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).