Return-Path: <cyrus@holtmann.org>
Subject: Re: Per-project patch prefixes
From: Bastien Nocera <hadess@hadess.net>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Date: Wed, 15 Jun 2011 00:48:29 +0100
In-Reply-To: <20110614211507.GB27437@piper>
References: <20110614211507.GB27437@piper>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <1308095312.9190.1.camel@air.hadess.net>
Mime-Version: 1.0
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

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...