From: Michael Buesch <mb@bu3sch.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Johannes Berg <johannes@sipsolutions.net>,
John Linville <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rfkill-input: remove unused code
Date: Fri, 27 Mar 2009 15:59:02 +0100 [thread overview]
Message-ID: <200903271559.02276.mb@bu3sch.de> (raw)
In-Reply-To: <20090327143608.GB24288@khazad-dum.debian.net>
On Friday 27 March 2009 15:36:08 Henrique de Moraes Holschuh wrote:
> On Fri, 27 Mar 2009, Johannes Berg wrote:
> > There's a lot of rfkill-input code that cannot ever be
> > compiled and is useless until somebody needs and tests
> > it -- therefore remove it.
>
> Just so that you guys know, that code *is* tested :-)
>
> I'd suggest that the code removal be done leaving a comment in place, like this:
>
> /* Currently, code to implement EV_SW SW_WLAN/WWAN/BLUETOOTH/etc is not
> * in place since it was unused and was therefore removed. Please look
> * at past history to check how it was supposed to be done, if you need
> * to implement handling for EV_SW.
> */
>
> Because that codepath is _not_ the most obvious thing in the world to
> reimplement without hitting a pitfall, so people better look how it was done
> once in time...
>
In practice this stuff does bitrot.
So in my opinion it's _not_ a good idea to lookup some old code for implementing
a feature. Instead one should think about it and understand the stuff and then implement it.
And if there are pitfalls that are not obvious after one completely read the code, one
should consider a redesign.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-03-27 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 13:16 [PATCH] rfkill-input: remove unused code Johannes Berg
2009-03-27 14:36 ` Henrique de Moraes Holschuh
2009-03-27 14:59 ` Michael Buesch [this message]
2009-03-27 15:13 ` Henrique de Moraes Holschuh
2009-03-27 15:11 ` Johannes Berg
2009-03-28 0:55 ` Henrique de Moraes Holschuh
2009-03-27 21:10 ` Johannes Berg
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=200903271559.02276.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--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