From: Bastien Nocera <hadess@hadess.net>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Per-project patch prefixes
Date: Wed, 15 Jun 2011 00:48:29 +0100 [thread overview]
Message-ID: <1308095312.9190.1.camel@air.hadess.net> (raw)
In-Reply-To: <20110614211507.GB27437@piper>
On Tue, 2011-06-14 at 18:15 -0300, Vinicius Costa Gomes wrote:
> Hi,
>
> 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:
>
>
> 1. kernel:
> - bluetooth-next -> for patches against Gustavo's bluetooth-next
> - bluetooth-current -> for patches against Gustavo's bluetooth-2.6
>
> 2. BlueZ:
> - bluez
>
> 3. obexd:
> - obexd
>
> This is just an idea, what do you think?
Or we could stop playing with mailing-lists and use bugzillas for the
non-kernel bits...
prev parent reply other threads:[~2011-06-14 23:48 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
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 [this message]
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=1308095312.9190.1.camel@air.hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--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