mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Horst von Brand" <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org,
	"Kalin KOZHUHAROV" <kalin@thinrope.net>,
	"Jesper Juhl" <jesper.juhl@gmail.com>, "Greg KH" <greg@kroah.com>
Subject: Re: Linux kernel development
Date: Sun, 4 Jun 2006 12:00:08 +0200	[thread overview]
Message-ID: <4d8e3fd30606040300w6d939f4csfe96829d3e5481a9@mail.gmail.com> (raw)
In-Reply-To: <200606031828.k53ISSgr012167@laptop11.inf.utfsm.cl>

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

  reply	other threads:[~2006-06-04 10:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 13:36 Paolo Ciarrocchi
2006-06-03 18:28 ` Horst von Brand
2006-06-04 10:00   ` Paolo Ciarrocchi [this message]
2006-06-04 10:30     ` Paolo Ciarrocchi
2006-06-04 23:05       ` Horst von Brand
2006-06-05 11:39         ` Paolo Ciarrocchi
2006-06-05 14:58           ` Steven Rostedt
2006-06-05 20:52             ` Paolo Ciarrocchi
2006-06-05 17:38           ` Horst von Brand
2006-06-05 20:51             ` Paolo Ciarrocchi
2006-06-06 19:22   ` Paolo Ciarrocchi
2006-06-06 22:09     ` Horst von Brand
2006-06-07 21:59       ` Paolo Ciarrocchi
2007-07-16 21:04 Linux Kernel Development Paolo Ciarrocchi
2007-07-16 21:34 ` Michal Piotrowski
2007-07-16 21:37   ` Paolo Ciarrocchi
     [not found] <CAK8ka9y1VhMzS0X2GSEg4AQzSMPwOkS3HQxBuX4t-Rp-_OwDow@mail.gmail.com>
2011-08-22  4:51 ` linux kernel development Niloofar Fazlollahi
2011-08-22  4:53   ` Américo Wang

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=4d8e3fd30606040300w6d939f4csfe96829d3e5481a9@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --cc=greg@kroah.com \
    --cc=jesper.juhl@gmail.com \
    --cc=kalin@thinrope.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®