From: Johannes Berg <johannes@sipsolutions.net>
To: "Vladimír Čunát" <vcunat@gmail.com>
Cc: linux-wireless@vger.kernel.org, Nix Dev <nix-dev@lists.science.uu.nl>
Subject: Re: broken URLs of iwlwifi firmware tarballs
Date: Wed, 04 Feb 2015 13:15:24 +0100 [thread overview]
Message-ID: <1423052124.4741.0.camel@sipsolutions.net> (raw)
In-Reply-To: <54D20B43.9060506@gmail.com> (sfid-20150204_130629_942767_BA1AA591)
On Wed, 2015-02-04 at 13:06 +0100, Vladimír Čunát wrote:
> On 02/03/2015 09:46 AM, Johannes Berg wrote:
> > I've fixed that now.
>
> Thanks!
>
> For future reference, is it the case that fetching from (c)git is the
> preferred way of distributing the firmware? (preferred by you, i.e.
> *.kernel.org)
We publish both, so it doesn't really matter.
johannes
next prev parent reply other threads:[~2015-02-04 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 21:48 broken URLs of iwlwifi firmware tarballs Vladimír Čunát
2015-02-02 22:45 ` Sven-Haegar Koch
2015-02-02 22:57 ` Vladimír Čunát
2015-02-03 8:46 ` Johannes Berg
2015-02-04 12:06 ` Vladimír Čunát
2015-02-04 12:15 ` Johannes Berg [this message]
2015-02-04 15:35 ` Emmanuel Grumbach
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=1423052124.4741.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nix-dev@lists.science.uu.nl \
--cc=vcunat@gmail.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).