public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC] HOWTO do Linux kernel development - take 2
Date: Tue, 15 Nov 2005 14:01:36 -0800	[thread overview]
Message-ID: <20051115220136.GA12413@suse.de> (raw)
In-Reply-To: <9a8748490511151406y72e82354w5c5599ea6201d38e@mail.gmail.com>

On Tue, Nov 15, 2005 at 11:06:04PM +0100, Jesper Juhl wrote:
> On 11/15/05, Greg KH <gregkh@suse.de> wrote:
> > Here's an updated version of the "HOTO do Linux kernel development"
> > document that I've been working on.
> >
> > For a description of why I started this, please see:
> >         http://thread.gmane.org/gmane.linux.kernel/348689
> >
> > I've addressed all of the comments that I have received, and flushed out
> > the the TODO sections.  I'd appreciate any comments on this version, as
> > I think it's looking pretty good and finished for now.  If no one
> > objects, I'll send it in a patch for inclusion in the main tree soon.
> >
> [snip]
> >
> >   Documentation/applying-patches.txt
> >     A good introduction describing exactly what a patch is, how to
> >     create it, and how to apply it to the different development branches
> >     of the kernel.
> >
> [snip]
> 
> I don't believe I mention anything about patch /creation/ in
> applying-patches.txt, at least the point of the document when I wrote
> it was to explain what a patch is, how to apply it and give a short
> description of the various trees.
> So, your description is accurate except for the "how to create it" bit.

Ah, you are right.  I was thinking of the SubmittingPatches file, that
is where we describe how to create a patch.

thanks for catching this, I've fixed it up.

greg k-h

  reply	other threads:[~2005-11-15 22:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 21:05 [RFC] HOWTO do Linux kernel development - take 2 Greg KH
2005-11-15 21:52 ` Avuton Olrich
2005-11-15 21:54   ` Greg KH
2005-11-16  5:31   ` Rogério Brito
2005-11-16  5:38     ` Greg KH
2005-11-15 22:06 ` Jesper Juhl
2005-11-15 22:01   ` Greg KH [this message]
2005-11-15 22:08 ` Andreas Schwab
2005-11-15 21:59   ` Greg KH
2005-11-15 22:21 ` Jesper Juhl
2005-11-15 22:30   ` Greg KH
2005-11-18  5:40     ` Jody McIntyre
2005-11-21 22:03       ` Greg KH
2005-11-15 22:27 ` Jesper Juhl
2005-11-15 22:36   ` Greg KH
2005-11-16  0:23 ` Adrian Bunk
2005-11-16  1:10   ` Greg KH
2005-11-16  1:46     ` Coywolf Qi Hunt
2005-11-16  2:01       ` Alistair John Strachan
2005-11-16  2:17     ` Adrian Bunk
2005-11-16  5:47       ` Greg KH
2005-11-16 17:28 ` David Woodhouse
2005-11-16 17:38   ` Randy.Dunlap
2005-11-16 17:40   ` Jörn Engel

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=20051115220136.GA12413@suse.de \
    --to=gregkh@suse.de \
    --cc=greg@kroah.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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