All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] some *seriously* deceased code in the tree
Date: Sat, 03 Feb 2007 16:57:41 +0000	[thread overview]
Message-ID: <20070203165741.GX7585@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702030436460.24858@CPE00045a9c397f-CM001225dbafb6>

On Sat, Feb 03, 2007 at 04:43:36AM -0500, Robert P. J. Day wrote:
> as one amusing example, i just ran across this in
> arch/parisc/mm/fault.c:
> 
> ======================> #if 0
> /* This is the treewalk to find a vma which is the highest that has
>  * a start < addr.  We're using find_vma_prev instead right now, but
>  * we might want to use this at some point in the future.  Probably
>  * not, but I want it committed to CVS so I don't lose it :-)
>  */
>                         while (tree != vm_avl_empty) {
>                                 if (tree->vm_start > addr) {
>                                         tree = tree->vm_avl_left;
>                                 } else {
>                                         prev = tree;
>                                         if (prev->vm_next = NULL)
>                                                 break;
>                                         if (prev->vm_next->vm_start > addr)
>                                                 break;
>                                         tree = tree->vm_avl_right;
>                                 }
>                         }
> #endif
> ======================> 
>   in the first place, how old does kernel code have to be to have been
> originally checked in via *CVS*?  :-)

The parisc-linux project switched from CVS to git in August 2006.
Since you asked so nicely, I originally checked in this code in December
2000, so it's just over 6 years old.

>   more importantly, though, this strikes me as a misuse of the
> official kernel tree -- as an archival dumping ground for snippets of
> code that have no immediate value but might someday be useful so, what
> the heck, let's throw it in there and, who knows, we might get back to
> it but maybe not.
> 
>   IMHO, that's the sort of thing that deserves to be ripped out
> without a moment's hesitation.

What harm does it do to leave it alone?  There's about a billion more
important things to spend time on than this.
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2007-02-03 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03  9:43 [KJ] some *seriously* deceased code in the tree Robert P. J. Day
2007-02-03 12:49 ` Tobias Klauser
2007-02-03 16:57 ` Matthew Wilcox [this message]
2007-02-03 17:16 ` 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=20070203165741.GX7585@parisc-linux.org \
    --to=matthew@wil.cx \
    --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.