Change of the bluetooth-next-2.6 tree

Change of the bluetooth-next-2.6 tree

[Gustavo F. Padovan]

Hi,

I want to request the change of the bluetooth for -next stuff in linux
tree. (didn't find other place better than this mailing list to request
this :) The new tree is at

git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git

Thanks,

-- 
Gustavo F. Padovan
ProFUSION embedded systems - http://profusion.mobi

Re: Change of the bluetooth-next-2.6 tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

Hi Gustavo,

On Thu, 14 Oct 2010 21:18:17 -0300 "Gustavo F. Padovan" <padovan@profusion.mobi> wrote:
>
> I want to request the change of the bluetooth for -next stuff in linux
> tree. (didn't find other place better than this mailing list to request
> this :) The new tree is at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git

Currently the bluetooth tree in linux-next is owned by Marcel - who is
also listed as the maintainer in the MAINTAINERS file.  I would need a
request from him (or an ack of this request) to change that.  Or some
other reason ...

Mind you, that tree was last updated in August.

I also think that Marcel used to get Dave Miller to merge his tree
instead of asking Linus' directly, so I guess Dave also needs to know
about this (unless he already does).
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: Change of the bluetooth-next-2.6 tree

[Marcel Holtmann]

Hi Stephen,

> > I want to request the change of the bluetooth for -next stuff in linux
> > tree. (didn't find other place better than this mailing list to request
> > this :) The new tree is at
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git
> 
> Currently the bluetooth tree in linux-next is owned by Marcel - who is
> also listed as the maintainer in the MAINTAINERS file.  I would need a
> request from him (or an ack of this request) to change that.  Or some
> other reason ...
> 
> Mind you, that tree was last updated in August.
> 
> I also think that Marcel used to get Dave Miller to merge his tree
> instead of asking Linus' directly, so I guess Dave also needs to know
> about this (unless he already does).

this is changing. Gustavo is taking over the tree maintenance. I will
still doing patch review for Bluetooth.

Regards

Marcel

Re: Change of the bluetooth-next-2.6 tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hi Marcel,

On Fri, 15 Oct 2010 10:02:16 +0300 Marcel Holtmann <marcel@holtmann.org> wrote:
>
> > > I want to request the change of the bluetooth for -next stuff in linux
> > > tree. (didn't find other place better than this mailing list to request
> > > this :) The new tree is at
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git
> > 
> > Currently the bluetooth tree in linux-next is owned by Marcel - who is
> > also listed as the maintainer in the MAINTAINERS file.  I would need a
> > request from him (or an ack of this request) to change that.  Or some
> > other reason ...
> > 
> > Mind you, that tree was last updated in August.
> > 
> > I also think that Marcel used to get Dave Miller to merge his tree
> > instead of asking Linus' directly, so I guess Dave also needs to know
> > about this (unless he already does).
> 
> this is changing. Gustavo is taking over the tree maintenance. I will
> still doing patch review for Bluetooth.

OK, I will change this for Monday.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: Change of the bluetooth-next-2.6 tree

[Gustavo F. Padovan]

Hi Stephen,

* Stephen Rothwell <sfr@canb.auug.org.au> [2010-10-15 17:45:02 +1100]:

> Hi Gustavo,
> 
> On Thu, 14 Oct 2010 21:18:17 -0300 "Gustavo F. Padovan" <padovan@profusion.mobi> wrote:
> >
> > I want to request the change of the bluetooth for -next stuff in linux
> > tree. (didn't find other place better than this mailing list to request
> > this :) The new tree is at
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git
> 
> Currently the bluetooth tree in linux-next is owned by Marcel - who is
> also listed as the maintainer in the MAINTAINERS file.  I would need a
> request from him (or an ack of this request) to change that.  Or some
> other reason ...

My mistake here for not saying the reason of the change. Sorry. 

-- 
Gustavo F. Padovan
ProFUSION embedded systems - http://profusion.mobi

Re: Change of the bluetooth-next-2.6 tree

[David Miller]

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 15 Oct 2010 17:45:02 +1100

> I also think that Marcel used to get Dave Miller to merge his tree
> instead of asking Linus' directly, so I guess Dave also needs to
> know about this (unless he already does).

I'm already fully aware :-)

Re: Change of the bluetooth-next-2.6 tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

Hi Gustavo,

On Thu, 14 Oct 2010 21:18:17 -0300 "Gustavo F. Padovan" <padovan@profusion.mobi> wrote:
>
> I want to request the change of the bluetooth for -next stuff in linux
> tree. (didn't find other place better than this mailing list to request
> this :) The new tree is at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]