Re: [RFC] HOWTO do Linux kernel development

[Coywolf Qi Hunt <coywolf@gmail.com>]

2005/11/15, Greg KH <greg@kroah.com>:
> On Tue, Nov 15, 2005 at 01:51:44PM +0800, Coywolf Qi Hunt wrote:
> > 2005/11/15, Greg KH <greg@kroah.com>:
> > > On Tue, Nov 15, 2005 at 09:08:30AM +0800, Coywolf Qi Hunt wrote:
> > > > 2005/11/15, Greg KH <gregkh@suse.de>:
> > > > > So, I've been working on a document for the past week or so to help
> > > > > alleviate a lot of these problems.  If nothing else, it should be a place
> > > > > where anyone can point someone to when they ask the common questions, or
> > > > > do something in the not-correct way.  I'd like to add this to the Linux
> > > > > kernel source tree, so it will be kept up to date over time, as things
> > > > > change (like the development process.)  Ideally I'd like to put it in
> > > > > the main directory as HOWTO, but I don't know how others feel about
> > > >
> > > > You put it in the top directory to draw the most attention? Compare to
> > > > source trees of other kernel projects, Linux source tree looks clean.
> > > > Please don't spoil that. What's wrong with Documentation/ ?
> > >
> > > People do not seem to even realize Documentation/ is there :(
> >
> > Those who don't notice Documentation, don't deserve it, and are not
> > likely/willingly to be the audience,
>
> Actually this is exactly the audience this is for, people who do not
> know where to look for the stuff they are trying to find.
>
> Now getting people to realize that this is the file they really want to
> look at is a different task, but not impossible.

Seriously doubt it. Or even they find the howto in top directory, they
aren't going to persevere in finishing reading it. So please keep it
as short as possible to full achieve your goal.

>
> > > Now if those same people would notice anything in the root directory
> > > either, is another story...
> >
> > That is rather like top-posting or CAPITALIZATION, or spamming.
>
> Cool, I'm a top-poster, SPAMMER for creating a HOWTO file in the root
> directory of the kernel tree.  And here I thought I had been called
> every bad name in the book before :)

np then, I've done my job as a reminder.
btw, also remember to add there a
tutorial-for-dummies-step-by-step-in-ten-days and the like.

>
> > > It's just a suggestion.
> >
> > We are unlikely to relocate files. So if it gets there, it'll stay
> > there all along.
>
> git makes it trivial to move files, so this is not true at all.

I mean we are unlikely/lazy to do relocation. So it's a
once-wrong-always-wrong thing.
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/