From: Johannes Berg <johannes@sipsolutions.net>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
"John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Anyone have a clone of wireless-legacy.git?
Date: Thu, 02 Jun 2016 21:59:50 +0200 [thread overview]
Message-ID: <1464897590.2169.12.camel@sipsolutions.net> (raw)
In-Reply-To: <20160602204808.3ff37346@lxorguk.ukuu.org.uk> (sfid-20160602_214851_014539_2B0EDA48)
On Thu, 2016-06-02 at 20:48 +0100, One Thousand Gnomes wrote:
> On Thu, 2 Jun 2016 14:38:04 -0400
> "John W. Linville" <linville@tuxdriver.com> wrote:
>
> >
> > It has recently come to my attention that the old wireless-
> > legacy.git
> > tree is no longer available on kernel.org. I honestly have no idea
> > what happened to it -- for all I know I fat-fingered it some time
> > ago or whatever. Anyway, apparently there are some references in
> > it
> > "out there" and it would be good if we had a copy available
> > somewhere
> > public.
> >
> > If you have an old clone of wireless-legacy.git, PLEASE DO NOT
> > DELETE
> > IT! Please let me know that you've got it and I will arrange to
> > get
> > a copy of it from you in order to make it available publicly again.
> Before you do that please make sure you get multiple copies from
> unconnected sources and confirm none of them are trojanned.
>
Not really necessary - at least one commit ID in it is well documented:
https://www.softwarefreedom.org/resources/2007/ath5k-code-analysis.html
That might very well be one of the last commits in that tree.
johannes
next prev parent reply other threads:[~2016-06-02 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 18:38 Anyone have a clone of wireless-legacy.git? John W. Linville
2016-06-02 19:48 ` One Thousand Gnomes
2016-06-02 19:59 ` Johannes Berg [this message]
2016-06-02 20:01 ` Johannes Berg
2016-06-02 20:00 ` John W. Linville
2016-06-03 1:18 ` Guenter Roeck
2016-06-03 7:06 ` Johannes Berg
2016-06-03 14:34 ` John W. Linville
2016-06-03 17:10 ` Guenter Roeck
2016-06-03 14:19 ` John W. Linville
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=1464897590.2169.12.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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).