Re: [PATCH 3/4] format-patch: new --resend option for adding "RESEND" to patch subjects
- From
Kristoffer Haugsbakk <code@khaugsbakk.name>
- Date
- Apr 17, 2024, 11:31 UTC
- Message-ID
- <d60e5ddd-643d-41f2-849d-6ab660df734c@app.fastmail.com>
- In-Reply-To
- <1f31004bd8445e1e4717817638d5509a@manjaro.org>
On Wed, Apr 17, 2024, at 12:52, Dragan Simic wrote:
Show 26 quoted lines
> Hello Phillip, > > On 2024-04-17 12:02, Phillip Wood wrote: >> On 17/04/2024 04:32, Dragan Simic wrote: >>> Add --resend as the new command-line option for "git format-patch" >>> that adds >>> "RESEND" as a (sub)suffix to the patch subject prefix, eventually >>> producing >>> "[PATCH RESEND]" as the default patch subject prefix. >>> >>> "[PATCH RESEND]" is a patch subject prefix commonly used on mailing >>> lists >>> for patches resent to a mailing list after they had attracted no >>> attention >>> for some time, usually for a couple of weeks. As such, this subject >>> prefix >>> deserves adding --resend as a new shorthand option to "git >>> format-patch". >> >> Playing devil's advocate for a minute, is this really common enough to >> justify a new option when the user can use "--subject-prefix='PATCH >> RESEND'" instead? > > Based on my experience, "[PATCH RESEND]" is roughly as commonly > used as "[PATCH RFC]". In other words, it obviously isn't used > as much as the good, old plain "[PATCH]", but it is used.
The format-patch generated string is `RFC PATCH`.
The number of emails with `PATCH RESEND` for this list:[1]
``` $ git log --oneline --fixed-strings --grep='[PATCH RESEND' | wc -l 28 ```
For RFC:
``` $ git log --oneline --fixed-strings --grep='[RFC PATCH' | wc -l 1181 ```
† 1: According to http://lore.kernel.org/git/1
-- Kristoffer Haugsbakk