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

Re: [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH]

From
Jacob Keller <jacob.keller@gmail.com>
Date
Sep 20, 2016, 06:50 UTC
Message-ID
<CA+P7+xoQSV99i0ntsw8P+p3K21FGCi9kkhqTq7tC3rSCMcLL5g@mail.gmail.com>
In-Reply-To
<20160920013704.7hk2creytmfrla6h@sigill.intra.peff.net>
On Mon, Sep 19, 2016 at 6:37 PM, Jeff King <peff@peff.net> wrote:
Show 18 quoted lines
> On Mon, Sep 19, 2016 at 04:40:22PM -0700, Josh Triplett wrote:
>
>> >   - there are a non-trivial number of patches for other projects (JGIT,
>> >     EGIT, StGit, etc). This is somewhat unique to git, where we discuss
>> >     a lot of related projects on the list. But I wonder if other
>> >     projects would use subsystems in a similar way (though I guess for
>> >     the kernel, there are separate subsystems lists, so the "to" or "cc"
>> >     header becomes the more interesting tag).
>>
>> The kernel mostly uses "[PATCH] subsystem: ...".  Occasionally I see
>> "[PATCH somegitrepo ...] ..." when it's necessary to explicitly say
>> whose git repo the patch needs to go through, but that's pretty rare.
>
> We do both. "foo: blah" is for subsystem "foo" of Git itself, but
> all-caps "JGIT PATCH" is "this is not even for Git". I don't know that
> the kernel really has an equivalent.
>
> -Peff
[net] and [net-next] are for the *tree* not the subsystem of the tree.

net: also means the networking subsystem, but it's different you might have a new feature and say

[net-next PATCH v2] net: my awesome new feature.

Thanks, Jake

Previous: Jeff KingNext: Jacob Keller
Message 13 of 14 in “format-patch: Add --rfc for the common case of [RFC PATCH]”
  1. format-patch: Add --rfc for the common case of [RFC PATCH]Josh Triplett, Sep 17, 2016
  2. Jeff KingSep 17, 2016
  3. Andrew DonnellanSep 19, 2016
  4. Junio C HamanoSep 19, 2016
  5. Josh TriplettSep 19, 2016
  6. Jeff KingSep 19, 2016
  7. Josh TriplettSep 19, 2016
  8. Jacob KellerSep 19, 2016
  9. Josh TriplettSep 19, 2016
  10. Jacob KellerSep 19, 2016
  11. Jeff KingSep 20, 2016
  12. Jeff KingSep 20, 2016
  13. Jacob KellerSep 20, 2016
  14. Jacob KellerSep 19, 2016

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.