From: Jeff King <peff@peff.net>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
git@vger.kernel.org
Subject: Re: [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH]
Date: Mon, 19 Sep 2016 18:37:04 -0700 [thread overview]
Message-ID: <20160920013704.7hk2creytmfrla6h@sigill.intra.peff.net> (raw)
In-Reply-To: <20160919234022.GA29421@cloud>
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
next prev parent reply other threads:[~2016-09-20 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 7:21 [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH] Josh Triplett
2016-09-17 18:43 ` Jeff King
2016-09-19 9:17 ` Andrew Donnellan
2016-09-19 17:49 ` Junio C Hamano
2016-09-19 20:44 ` Josh Triplett
2016-09-19 23:34 ` Jeff King
2016-09-19 23:40 ` Josh Triplett
2016-09-19 23:46 ` Jacob Keller
2016-09-19 23:55 ` Josh Triplett
2016-09-19 23:57 ` Jacob Keller
2016-09-20 1:37 ` Jeff King
2016-09-20 1:37 ` Jeff King [this message]
2016-09-20 6:50 ` Jacob Keller
2016-09-19 23:44 ` Jacob Keller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160920013704.7hk2creytmfrla6h@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andrew.donnellan@au1.ibm.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=josh@joshtriplett.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).