Re: [RFC/git patch] move samples/ to Documentation/markers/

From: Sam Ravnborg
Date: Wed Oct 24 2007 - 12:16:19 EST


On Wed, Oct 24, 2007 at 09:12:40AM -0700, Randy Dunlap wrote:
> On Wed, 24 Oct 2007 09:19:05 -0400 Jeff Garzik wrote:
>
> > Honestly, I don't care at all about building the code. If that's what
> > you want, great.
>
> Yes, that is wanted. They bitrot too easily -- not good.
>
> > My objection is more to adding a samples/ directory, which is contra to
> > past experience:
> >
> > A new net driver sample should go in drivers/net/ like the existing
> > skeleton files I already listed, not samples/net/. A top-level
>
> Can't disagree with that.
>
> > "samples/" seems like it exists only duplicate the rest of the tree
> > hierarchy.
>
> It seems odd to be building code in Documentation/, but I can live
> with that. It was primarily Christoph who was opposed to that.
> He suggested samples/ and I went along with it just to break the
> impasse (since no one else was making any comments on it at that
> time).
>
> Sam, would building code in Documentation/ cause problems for
> kbuild?
I have this pipe dream that we shall introduce a tool to make the
.txt doc readable in some popular format (HTML?) and then we would
have that Makefile in Documentation/ but that could be a special target
so should be OK.

Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/