All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Drebes <lists-receive@programmierforen.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Why keeping lines commented out via #if 0?
Date: Sat, 02 Jun 2007 18:00:07 +0000	[thread overview]
Message-ID: <200706022000.07655.lists-receive@programmierforen.de> (raw)
In-Reply-To: <200706021359.23564.lists-receive@programmierforen.de>

>   some thoughts on how much of the "#if 0" stuff can be removed.
> first, in a lot of cases, there's little you can do.  there will be
> some code that has been commented out, with no indication as to why
> that was done.
ok, now I'm cautious with my comments because the discussion became
quite emotional (the change of views between Matthew and you). However,
I think that if there's no indication why the code was commented out and
if even the maintainer doesn't know why, I think it is quite clear that the
affected lines should be removed, because the collective memory of the
community has forgotten why it was done. If nobody knows it, I think that
nobody will ever use this code again.

> if you're lucky, you might be able to recognize that 
> the "removed" code represents a clearly deprecated or obsolete kernel
> construct, in which case you can certainly take a shot at putting
> together a patch and just emailing it offline to the respective
> subsystem maintainer.
>   i've had good luck with that -- if you're not sure about the patch,
> there's no point posting it to the whole list, just send it to the
> maintainer and ask for some feedback.  in some cases, they'll just
> add it to their local tree and you're done.
The next time I encounter lines commented out with #if 0 and I detect something
like that, I'll follow your advice.
 
>   in other cases, there's obviously something weird going on and, if
> you want to follow up, you might need to do some detective work.  
<snip>
> in cases like that, a short email to one of the 
> maintainers might clear things up.
ok.

>   there's no one formula for this sort of cleanup, and it's typically
> compounded by the fact that developers are outrageously possessive of
> their code, even if it's years old and rotting.  best advice:  just
> start perusing and pick something that looks obvious.
ok.

	Andi
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2007-06-02 18:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 11:59 [KJ] Why keeping lines commented out via #if 0? Andi Drebes
2007-06-02 13:15 ` Robert P. J. Day
2007-06-02 14:59 ` Matthew Wilcox
2007-06-02 15:29 ` Robert P. J. Day
2007-06-02 15:47 ` Matthew Wilcox
2007-06-02 16:48 ` Robert P. J. Day
2007-06-02 18:00 ` Andi Drebes [this message]
2007-06-02 18:13 ` Arnaldo Carvalho de Melo
2007-06-02 18:31 ` Andi Drebes
2007-06-02 18:47 ` Thomas De Schampheleire
2007-06-03  8:09 ` Robert P. J. Day
2007-06-03  9:12 ` Rene Herman
2007-06-03 10:47 ` Andi Drebes
2007-07-02 10:43 ` Vegard Nossum
2007-07-02 11:07 ` Robert P. J. Day

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=200706022000.07655.lists-receive@programmierforen.de \
    --to=lists-receive@programmierforen.de \
    --cc=kernel-janitors@vger.kernel.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 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.