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

<snip>
> Ofcourse, noone should go overboard with it but people don't. If something has 
> no value anymore, it's deleted. It's only kept as a comment when it _is_ seen to 
> have value in some or other form and as such deleting it is not a janitorial 
> task but something that needs a maintainer. If the code sees active maintainance 
> it still being there already means it's seen to still have value and if the code 
> does not, it should most certainly be left alone as documentation for a possible 
> next person stepping in.
> 
> A suggestion that any #if 0 code should preferably have a comment describing why 
> it's there would ofcourse not be bad.
Yes, I totally agree with that. Especially for people that are new to kernel stuff (me, for example)
are quite confused about the fact that there's so much code commented out. Just a
short and descriptive line that tells people why this was commented out would be very
nice and helpful.

	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-03 10:47 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
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 [this message]
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=200706031247.24340.webmaster@programmierforen.de \
    --to=webmaster@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.