From: Mat Martineau <mathewm@codeaurora.org>
To: marcel@holtmann.org, Gustavo Padovan <padovan@profusion.mobi>,
johan.hedberg@gmail.com
Cc: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: Current bluetooth tree: Was: pull request 2012-03-08
Date: Thu, 8 Mar 2012 09:38:08 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1203080927240.13102@mathewm-linux> (raw)
In-Reply-To: <20120308082242.GB26562@aemeltch-MOBL1>
On Thu, 8 Mar 2012, Andrei Emeltchenko wrote:
> Hi,
>
> On Thu, Mar 08, 2012 at 02:44:31AM -0300, Gustavo Padovan wrote:
>> are available in the git repository at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next master
>
> Is this current bluetooth-next tree?
So I'm not the only one confused by the current setup with two
bluetooth-nexts!
Marcel, Gustavo, and Johan, can you please let the list know exactly
what is going on with the kernel trees? The last official word we had
was that Johan's temporary tree was in use while Gustavo was taking a
break -- but Gustavo is back, Johan is still accepting patches, and
David Miller is pulling from Gustavo's tree...
Right now Gustavo's tree is more up to date because it includes David
Miller's merge to net-next. Are we switching back to
git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next
now?
--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2012-03-08 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 5:44 pull request: bluetooth-next 2012-03-08 Gustavo Padovan
2012-03-08 6:57 ` David Miller
2012-03-08 8:22 ` Current bluetooth tree: Was: pull request 2012-03-08 Andrei Emeltchenko
2012-03-08 17:38 ` Mat Martineau [this message]
2012-03-08 18:20 ` Gustavo Padovan
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=alpine.DEB.2.02.1203080927240.13102@mathewm-linux \
--to=mathewm@codeaurora.org \
--cc=andrei.emeltchenko.news@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
/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