From: Florian Mickler <florian@mickler.org>
To: Thomas Winkler <tomasw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: New iwlwifi 3945 uCode available
Date: Fri, 24 Oct 2008 14:45:21 +0200 [thread overview]
Message-ID: <20081024144521.3943a0a3@schatten> (raw)
In-Reply-To: <1ba2fa240810220528w6b2e4e60k7d2390328d9b5c49@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
Hi!
I'm a 3945 user and am quite happy with everything. Thx for your good
work! But:
On Wed, 22 Oct 2008 14:28:14 +0200
"Tomas Winkler" <tomasw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> The objective of the objections is not that we want to immensely hurt
> users but rather the trade off between maintain even uglier code and
> users running buggy firmware versus logging into older kernel and
> downloading new firmware in 5 minutes looks to me not proportional.
> Distro users that pull updates won't even notice. I might be wrong
> though.
more so like 10 minutes, if you are quick to grasp what happened.
if 1000 encounter this problem, that's 10000 minutes wasted, thats
7*24 hours. That's some annoying big waste of time!
keep in mind that that breakage _will_ waste the time of other people
and that those people are your fellow cutting-edge-kernel testers and
developers!
but then again, if the new firmware is really superior in many cases,
that might be worth it? i mean, if people forget that they are annoyed
because the device now performs super ueber cool... or smth like that..
it might pay off (from a user perspective)...
so my hope: you avoid breakage and keep people happy! That
is also good for your karma (whatever that is)
Sincerely,
Florian
p.s.: if i think more about it: all my non-linux colleagues refer to
such breakages as "the linux-expirience"... my linux friends would refer
to such stuff as "the gentoo-expirience" ... but in my book stuff
like this just sucks...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-24 13:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 18:27 New iwlwifi 3945 uCode available reinette chatre
2008-10-21 21:25 ` Johannes Berg
2008-10-21 21:33 ` Tomas Winkler
2008-10-21 21:34 ` Johannes Berg
2008-10-21 21:38 ` John W. Linville
2008-10-21 21:53 ` Tomas Winkler
2008-10-21 22:13 ` Marcel Holtmann
2008-10-21 22:23 ` Tomas Winkler
2008-10-21 23:01 ` Marcel Holtmann
2008-10-21 23:09 ` Luis R. Rodriguez
2008-10-21 23:11 ` Marcel Holtmann
2008-10-21 23:27 ` Luis R. Rodriguez
2008-10-21 23:31 ` Marcel Holtmann
2008-10-21 23:34 ` Luis R. Rodriguez
2008-10-21 22:28 ` reinette chatre
2008-10-21 23:06 ` Marcel Holtmann
2008-10-21 23:34 ` Tomas Winkler
2008-10-22 1:03 ` Marcel Holtmann
2008-10-22 7:27 ` Johannes Berg
2008-10-22 7:56 ` Marcel Holtmann
2008-10-22 7:57 ` Johannes Berg
2008-10-22 20:30 ` reinette chatre
2008-10-22 22:59 ` Marcel Holtmann
2008-10-22 23:14 ` reinette chatre
2008-10-22 23:39 ` John W. Linville
2008-10-23 1:12 ` Marcel Holtmann
2008-10-23 7:22 ` Johannes Berg
2008-10-22 9:10 ` Tomas Winkler
2008-10-22 9:14 ` Johannes Berg
2008-10-22 9:23 ` Tomas Winkler
2008-10-22 10:07 ` Christoph Hellwig
2008-10-22 12:28 ` Tomas Winkler
2008-10-22 18:25 ` Marcel Holtmann
2008-10-24 12:45 ` Florian Mickler [this message]
2008-10-21 21:59 ` reinette chatre
-- strict thread matches above, loose matches on Subject: below --
2009-04-28 20:52 new " reinette chatre
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=20081024144521.3943a0a3@schatten \
--to=florian@mickler.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).