From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: tree borkage on git.kernel.org
Date: Tue, 2 Nov 2010 13:55:28 -0400 [thread overview]
Message-ID: <20101102175528.GC2425@tuxdriver.com> (raw)
There was some sort of IT hiccup on kernel.org overnight, and at
least the wireless trees (and probably others) there got restored
from several days prior. If you cloned or pulled the wireless trees
in the last 48 hours or so, you should consider doing it again now.
In particular, you might also note that wireless-testing has been
rebased on 2.6.37-rc1...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next reply other threads:[~2010-11-02 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 17:55 John W. Linville [this message]
2010-11-02 18:33 ` tree borkage on git.kernel.org 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=20101102175528.GC2425@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
/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).