From: "Strawbridge, Michael" <Michael.Strawbridge@amd.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: [Proposal] Pass additional metadata to sendemail-validate hook from git send-email
Date: Fri, 26 Aug 2022 21:00:25 +0000 [thread overview]
Message-ID: <87czcm7maf.fsf@amd.com> (raw)
Hi,
I was hoping to put a feature proposal forward for git send-email.
For git send-email there is a git hook, sendemail-validate which
gets the body of the email that will be sent but is missing some
of the metadata that git send-email has access to. I propose that
we also pass the extra metadata that gets presented to the user
later on via stdout such as: From, To, Cc, Subject, Date,
Message-Id, X-Mailer, MIME-Version, Content-Transfer-Encoding to
the git hook.
I'm willing to work on the patch but want to make sure the idea
would be accepted first.
Thank you,
Michael
next reply other threads:[~2022-08-26 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 21:00 Strawbridge, Michael [this message]
2022-08-28 0:39 ` [Proposal] Pass additional metadata to sendemail-validate hook from git send-emailg brian m. carlson
2022-08-29 15:37 ` [Proposal] Pass additional metadata to sendemail-validate hook from git send-email Strawbridge, Michael
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czcm7maf.fsf@amd.com \
--to=michael.strawbridge@amd.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).