linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-wireless@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Temporary(?) relocation of wireless git trees...
Date: Tue, 13 Sep 2011 09:29:46 -0400	[thread overview]
Message-ID: <20110913132946.GC11772@tuxdriver.com> (raw)
In-Reply-To: <20110913105858.eedd5ac594679aa36111c9d4@canb.auug.org.au>

On Tue, Sep 13, 2011 at 10:58:58AM +1000, Stephen Rothwell wrote:
> Hi John,
> 
> On Mon, 12 Sep 2011 14:13:52 -0400 "John W. Linville" <linville@tuxdriver.com> wrote:
> >
> > With no news on when the kernel.org trees will be accessible again
> > (which could be 10 minutes from now for all I know), I have pushed
> > my local copies to Infradead.  This should be equivalent to what was
> > last pushed to kernel.org almost two weeks ago.
> > 
> > The "current" wireless tree is here:
> > 
> > 	git://git.infradead.org/users/linville/wireless.git
> > 
> > The "next" wireless tree is here:
> > 
> > 	git://git.infradead.org/users/linville/wireless-next.git
> 
> OK, I have switched to these using their "master" branches.  There is
> nothing new in them, correct?

Yes, correct.  Hopefully more new stuff today...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2011-09-13 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 18:13 Temporary(?) relocation of wireless git trees John W. Linville
2011-09-13  0:58 ` Stephen Rothwell
2011-09-13 13:29   ` John W. Linville [this message]
2011-10-27 19:32 ` Ben Greear

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=20110913132946.GC11772@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).