On 6/3/06, Horst von Brand <vonbrand@inf.utfsm.cl> wrote:
> Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> > On 11/15/05, Greg KH <greg@kroah.com> wrote:
> > [...]
> > > > http://linux.tar.bz/articles/2.6-development_process
> > >
> > > Ah, a very nice summary.
> > >
> > > Paolo, can I use this document as a base for this section in the HOWTO
> > > file (with proper attribution of course.)
> >
> > That article is now living in a git tree, it now contains only spell
> > checks but I plan to work more on it in the next few days.
>
> I'd break it up into logical pieces (i.e., chapters...)

Yup, already in my todo list.

> The lines are way too long for easy reading.

Ok, I'll try to work on it.

> There are several other tools to check kernel quality: sparse, the
> lockcheck, ... And don't forget about the various debugging config options

Mmmh... Right, but the goal of the document was mainly to document the
process not the tools. However, that's a good comment.

> There are required tools for serious kernel development, i.e. git and its
> entournage. Link to them.

Ok.

> You mention that patches cook in -mm for a while, but you don't tell what
> that is beforehand. In general, a high-level overview of the current
> git-based development would be useful, and the various important git kernel
> trees and the patch flow among them.

Ok.

> Don't be shy in mentioning the stuff under Documentation in your nearest
> kernel source!

Right.

> Perhaps do an asccidoc format, to be able to create HTML?

Sure, but I don't know how to do it.

Patches are more then welcome :-)

Thank you for your valuable comments!!

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