On 2024-04-17 13:34, Dragan Simic wrote:
On 2024-04-17 13:31, Kristoffer Haugsbakk wrote:
On Wed, Apr 17, 2024, at 12:52, Dragan Simic wrote:
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`.
True. It's just that I more often see "PATCH RFC", for some reason.
Please note that I'm also taking other mailing lists into account.
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
I wonder what does it say for "RESEND" only?
Here are some numbers pulled from https://lore.kernel.org/linux-kernel/:
- "RFC": ~400,000
- "PATCH RFC": ~50,000
- "RFC PATCH": ~200,000
- "RESEND": ~200,000
- "PATCH RESEND": ~30,000
- "RESEND PATCH": ~30,000
Though, I'm not sure how accurate those numbers are. Even a cursory
look at the produced search results shows inaccuracy of the search
matches. There's probably some "fuzzy logic" at play there.
