From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Robin Jarry <robin@jarry.cc>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] hooks: add sendemail-validate-series
Date: Sat, 1 Apr 2023 09:54:08 +0700 [thread overview]
Message-ID: <9a0948e2-d030-ac89-a009-9247054f71f9@gmail.com> (raw)
In-Reply-To: <20230103231133.64050-1-robin@jarry.cc>
On 1/4/23 06:11, Robin Jarry wrote:
> +sendemail-validate-series
> +~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +This hook is invoked by linkgit:git-send-email[1]. It allows performing
> +validation on a complete patch series at once, instead of patch by patch with
> +`sendemail-validate`.
> +
> +`sendemail-validate-series` takes no arguments, but for each e-mail to be sent
> +it receives on standard input a line of the format:
> +
> + <patch-file> LF
> +
> +where `<patch-file>` is a name of a file that holds an e-mail to be sent,
> +
In most cases, the patch series is generated by git-format-patch(1). When the
command is run, it will output:
```
$ git format-patch -o /tmp --cover-letter --base=<base-commit> <base-commit>
/tmp/0000-cover-letter.patch
/tmp/0001-<patch-subject>.patch
/tmp/0002-<patch-subject>.patch
/tmp/0003-<patch-subject>.patch
...
```
The output can be fed to the hook (as you write).
But I think the hook should also take patch file arguments, for the sake of
completeness with sendemail-validate hook; that is:
```
sendemail-validate-series <patch file>...
```
Also, there should have a check that In-Reply-To must be the first patch in
the given series or the cover letter (if there is one).
Anyway, rather than pinging by random people, I'd like to see [PATCH RESEND],
rebased on latest git.git tree, ideally with Junio Cc'ed.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-04-01 2:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 23:11 [PATCH] hooks: add sendemail-validate-series Robin Jarry
2023-01-20 16:34 ` Robin Jarry
2023-02-27 14:03 ` Tim Culverhouse
2023-03-31 13:50 ` Nicolas Dichtel
2023-04-01 2:54 ` Bagas Sanjaya [this message]
2023-04-02 18:50 ` Robin Jarry
2023-04-03 0:05 ` Eric Sunshine
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a0948e2-d030-ac89-a009-9247054f71f9@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin@jarry.cc \
/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://80x24.org/mirrors/git.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).