git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC][RFC PATCH 0/6] Add --subject-extra-prefix flag to format-patch

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 5, 2025, 02:06 UTC
Message-ID
<xmqqo6ygmdst.fsf@gitster.g>
In-Reply-To
<7350D94E-39DC-4C9B-926A-3FA2A4C76687@gmail.com>
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com> writes:
Show 7 quoted lines
>> Once you stop treating [GSoC] as if it is an independent prefix,
>> everything will fall into place naturally without adding anything
>> extra.
>
> So, instead of changing the behavior of format-patch, would it be
> better if we changed the documentation to ask these patches to be
> sent with `[GSoC PATCH]` or similar instead of `[GSoC][PATCH]`?

Yup, I do not know offhand who are managing these descriptions, but having extra moniker in the same [square bracket] as PATCH is a more common practice, and we should follow suit.

Thanks.
Previous: Lucas Seiki OshiroNext: Lucas Seiki Oshiro
Message 14 of 15 in “Add --subject-extra-prefix flag to format-patch”
  1. Lucas Seiki OshiroMar 3, 2025
  2. [GSoC][RFC PATCH 1/6] builtin/log: add subject-extra-prefix flag to format-patchLucas Seiki Oshiro, Mar 3, 2025
  3. [GSoC][RFC PATCH 2/6] builtin/log: die if -k and --suject-extra-prefix are used togetherLucas Seiki Oshiro, Mar 3, 2025
  4. Eric SunshineMar 3, 2025
  5. [GSoC][RFC PATCH 3/6] revision: add subject_extra_field to struct rev_infoLucas Seiki Oshiro, Mar 3, 2025
  6. [GSoC][RFC PATCH 4/6] builtin/log: fill subject extra prefix in format-patchLucas Seiki Oshiro, Mar 3, 2025
  7. [GSoC][RFC PATCH 5/6] log-tree: add subject prefix in output email subjectLucas Seiki Oshiro, Mar 3, 2025
  8. [GSoC][RFC PATCH 6/6] t4014: add tests for the new flag --subject-extra-prefixLucas Seiki Oshiro, Mar 3, 2025
  9. Junio C HamanoMar 3, 2025
  10. Patrick SteinhardtMar 4, 2025
  11. Junio C HamanoMar 4, 2025
  12. Junio C HamanoMar 4, 2025
  13. Lucas Seiki OshiroMar 4, 2025
  14. Junio C HamanoMar 5, 2025
  15. Lucas Seiki OshiroMar 5, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.