From: "John W. Linville" <linville@tuxdriver.com>
To: Gustavo Padovan <padovan@profusion.mobi>
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2011-10-17
Date: Tue, 8 Nov 2011 15:58:25 -0500 [thread overview]
Message-ID: <20111108205824.GA2550@tuxdriver.com> (raw)
In-Reply-To: <20111017203900.GE2631@joana>
On Mon, Oct 17, 2011 at 06:39:01PM -0200, Gustavo Padovan wrote:
> As the 3.1 release is taking too long to happen I decided to send you another
> pull request. If you think it's too late just ignore it, or queue it up for
> 3.3 merge window. Do what is better to you. ;)
Well, I did think it was too late so I didn't pull it. I went to
pull it today, but it seems there is some newer stuff on top. Worse,
that newer stuff seems to cause conflicts. :-(
I'll just take the "ignore it" option for now until your next pull
request. :-)
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-11-08 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 20:39 pull request: bluetooth-next 2011-10-17 Gustavo Padovan
2011-11-08 20:58 ` John W. Linville [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=20111108205824.GA2550@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).