[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090122161659.53de9e56.akpm@linux-foundation.org>
Date: Thu, 22 Jan 2009 16:16:59 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dave Jones <davej@...hat.com>
Cc: gregkh@...e.de, mingo@...e.hu, geert@...ux-m68k.org,
joern@...fs.org, lkml@...idb.org, kernel@...uxace.com,
kay.sievers@...y.org, phillip@...gher.demon.co.uk,
hch@...radead.org, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29
> On Thu, 22 Jan 2009 16:50:41 -0500 Dave Jones <davej@...hat.com> wrote:
> I don't mean to piss on your parade, but from my viewpoint, staging
> is a trainwreck so far, and I'd hate to see it get worse.
I must say that I have intense "wtf were we thinking of" moments each time
something in staging/ sticks an ugly head out of its cave.
My question is: what is the process for moving things out of staging/ and
into the kernel proper? We don't want to be merging ex-crap code which has
had its whitespace and wrappers cleaned up by a person who is not suitably
experienced in the relevant subsystem.
It _should_ (I think) be "OK, this is ready for us to start reviewing".
ie: treat it as if it had just come in from a random new submitter.
a) If that happens, who will be responding to the review comments? Who
was the submitter?
b) What happens if it is then decided that we just don't want that code
in the tree at all?
c) Has any code yet made the transition out of staging and into the
kernel proper? If so, which?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists