From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>, git@vger.kernel.org
Subject: Re: [GSoC][RFC PATCH 0/6] Add --subject-extra-prefix flag to format-patch
Date: Tue, 04 Mar 2025 14:06:43 -0800 [thread overview]
Message-ID: <xmqq5xkoo3gs.fsf@gitster.g> (raw)
In-Reply-To: <Z8aspywaD0mAyHwd@pks.im> (Patrick Steinhardt's message of "Tue, 4 Mar 2025 08:32:55 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> I do understand though that `--rfc=GSoC` is not exactly discoverable for
> a newcomer. Maybe a simpler fix would be to introduce an alias for that
> option that is more discoverable? I don't have a great idea for how to
> name it -- the best that comes to mind is `--patch-prefix`, which
> mirrors `--subject-prefix`.
The problem with it is that having "patch" vs "subject" prefix will
make it confusing which one is which.
Let's step back and examine what we already have.
* The "--subject-prefix" is configurable and format.subjectPrefix
is meant to go to .git/config for repositories that work with
projects with special needs (they tell you to use not [PATCH] but
subproject specific moniker like [PATCH rcu] instead).
* The "--rfc[=<word>]" has no configuration and it is deliberately
so, as it is meant to be used as needed, on occasions that call
for it, pretty much decided per invocation.
Are these two points above not clear in our documentation? If so,
we should fix it, but I do not think giving a synonym to --rfc is a
good way to clarify it.
If it is a GSoC topic sent to this list, it _will_ be GSoC topic for
the entire iterations of the same topic. So it would be good to use
--subject-prefix="GSoC PATCH" (or configure format.subjectPrefix in
the repository to use that, if a student works with us only on GSoC
topics during the Summer-of-Code program duration), and on occasion,
when students are not so sure about their patches (yet), use of --rfc
would be a good way, which would give us "[RFC GSoC PATCH 0/6]", to
mark the patches as such.
Another problem with --patch-prefix synonym is that --rfc is not
necessarily a prefix. With
git format-patch --rfc='-WIP' --subject-prefix='GSoC PATCH'
you would get "[GSoC PATCH WIP 0/6]" instead.
In any case, I think it is the root cause of this disease to treat
GSoC mark as something extra that requires a new marker that is
separate from the usual PATCH marker. Using whatever mechanism you
would use your string in place for the standard PATCH mark to make
it say "GSoC PATCH" would be the most appropriate, without mucking
with an extra option, be it '--rfc' or '--subject-extra-prefix', I
would say.
Thanks.
next prev parent reply other threads:[~2025-03-04 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 22:00 [GSoC][RFC PATCH 0/6] Add --subject-extra-prefix flag to format-patch Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 1/6] builtin/log: add subject-extra-prefix " Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 2/6] builtin/log: die if -k and --suject-extra-prefix are used together Lucas Seiki Oshiro
2025-03-03 22:36 ` Eric Sunshine
2025-03-03 22:00 ` [GSoC][RFC PATCH 3/6] revision: add subject_extra_field to struct rev_info Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 4/6] builtin/log: fill subject extra prefix in format-patch Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 5/6] log-tree: add subject prefix in output email subject Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 6/6] t4014: add tests for the new flag --subject-extra-prefix Lucas Seiki Oshiro
2025-03-03 23:08 ` [GSoC][RFC PATCH 0/6] Add --subject-extra-prefix flag to format-patch Junio C Hamano
2025-03-04 7:32 ` Patrick Steinhardt
2025-03-04 22:06 ` Junio C Hamano [this message]
2025-03-04 13:05 ` Junio C Hamano
2025-03-04 23:19 ` Lucas Seiki Oshiro
2025-03-05 2:06 ` Junio C Hamano
2025-03-05 14:26 ` Lucas Seiki Oshiro
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=xmqq5xkoo3gs.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lucasseikioshiro@gmail.com \
--cc=ps@pks.im \
/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).