From: Ben Greear <greearb@candelatech.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: tree borkage on git.kernel.org
Date: Tue, 02 Nov 2010 11:33:16 -0700 [thread overview]
Message-ID: <4CD0596C.6080602@candelatech.com> (raw)
In-Reply-To: <20101102175528.GC2425@tuxdriver.com>
On 11/02/2010 10:55 AM, John W. Linville wrote:
> 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...
Are you ready to start accepting patches for wireless-testing again?
Can you please let us know when you expect to have the current
patch backlog (if there is one) pushed to wireless-testing?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-11-02 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 17:55 tree borkage on git.kernel.org John W. Linville
2010-11-02 18:33 ` Ben Greear [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=4CD0596C.6080602@candelatech.com \
--to=greearb@candelatech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.