From: Marcel Holtmann <marcel@holtmann.org>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: Per-project patch prefixes
Date: Wed, 15 Jun 2011 04:10:28 -0700 [thread overview]
Message-ID: <1308136231.2518.5.camel@aeonflux> (raw)
In-Reply-To: <20110614213143.GD2613@joana>
Hi Gustavo,
> > Now, this list receives patches for at least 3 different projects, so how
> > about using different subject prefixes for each priject? The first thing
> > that comes to mind is this:
>
> This is a great idea. It can a lot when identifying patches, and you can do
> this to the project's .git/config:
>
> [format]
> subjectprefix = "bluetooth-next"
as long as patches come in as [PATCH bluetooth-next v2] or something
similar I am fine with this. I want the [PATCH ...] prefix kept alive
since that is one thing that git did right from the beginning.
Regards
Marcel
next prev parent reply other threads:[~2011-06-15 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 21:15 Per-project patch prefixes Vinicius Costa Gomes
2011-06-14 21:31 ` Gustavo F. Padovan
2011-06-15 11:10 ` Marcel Holtmann [this message]
2011-06-15 12:04 ` Johan Hedberg
2011-06-15 18:13 ` Gustavo F. Padovan
2011-06-15 12:05 ` Luiz Augusto von Dentz
2011-06-14 23:48 ` Bastien Nocera
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=1308136231.2518.5.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=vinicius.gomes@openbossa.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox