From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Please pull 'upstream' branch of wireless-2.6 (actually 'for-jgarzik')
Date: Tue, 24 Apr 2007 13:57:23 -0400 [thread overview]
Message-ID: <462E4503.5020701@garzik.org> (raw)
In-Reply-To: <20070410202451.GD14123@tuxdriver.com>
John W. Linville wrote:
> Jeff,
>
> I branched off netdev-2.6#upstream, pulled my upstream into it, and
> resolved the conflicts. So, you probably want to pull from here
> instead:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git for-jgarzik
>
> FWIW, this also includes the patches from the pull request posted on
> 27 March 2007:
>
> http://marc.info/?l=linux-wireless&m=117514552402407&w=2
pulled
next prev parent reply other threads:[~2007-04-24 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 20:23 Please pull 'upstream-fixes' branch of wireless-2.6 John W. Linville
2007-04-10 20:24 ` Please pull 'upstream' branch of wireless-2.6 (actually 'for-jgarzik') John W. Linville
2007-04-24 17:57 ` Jeff Garzik [this message]
2007-04-11 15:58 ` Please pull 'upstream-fixes' branch of wireless-2.6 Jeff Garzik
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=462E4503.5020701@garzik.org \
--to=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).