public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Bodo Eggert <7eggert@gmx.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	Rolf Eike Beer <eike-kernel@sf-tec.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sean Bruno <sean.bruno@dsl-only.net>,
	Lee Revell <rlrevell@joe-job.com>,
	Gene Heskett <gene.heskett@verizon.net>,
	"H. Peter Anvin" <hpa@zytor.com>,
	David Brown <dmlb2000@gmail.com>,
	Puneet Vyas <vyas.puneet@gmail.com>,
	Richard Hubbell <richard.hubbell@gmail.com>,
	webmaster@kernel.org
Subject: Re: Documentation - how to apply patches for various trees
Date: Thu, 4 Aug 2005 01:19:19 +0200	[thread overview]
Message-ID: <200508040119.20289.jesper.juhl@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508032257080.3158@be1.lrz>

On Wednesday 03 August 2005 23:46, Bodo Eggert wrote:
> On Wed, 3 Aug 2005, Jesper Juhl wrote:
> 
> > +What is a patch?
> 
> > +To correctly apply a patch you need to know what base it was generated from
> > +and what new version the patch will change the source tree into. These
> > +should both be present in the patch file metadata.
> 
> This is usurally not true for kernel patches, the directories are mostly
> named a and b. You can however deduce the to-bepatched version and the
> patched version from the filename.
> 
hmm, I'd say the patch filename could be considered "metadata" as well.


> [...]
> 
> Or: bzcat patch1 patch2 patch3 | (cd linux-oldversion && patch -p1)
> 
yes, there are many ways, impossible to list them all, but this might be a
good example to add, just to show application of several patches in one go.

> 
<snip lots of good stuff>

I need to get some sleep now, but I'll add most of your text to the document
tomorrow and post a new patch.

Thanks!


-- 
Jesper


  reply	other threads:[~2005-08-03 23:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 21:32 Documentation - how to apply patches for various trees Jesper Juhl
2005-08-02 22:38 ` Randy.Dunlap
2005-08-03  1:05 ` Richard Hubbell
2005-08-03  2:00 ` Puneet Vyas
2005-08-03  6:40 ` Rolf Eike Beer
2005-08-03 14:44   ` Randy.Dunlap
     [not found]     ` <200508032251.07996.jesper.juhl@gmail.com>
2005-08-03 21:08       ` Linus Torvalds
2005-08-03 21:28         ` Jesper Juhl
2005-08-03 23:56           ` Johannes Stezenbach
2005-08-04  0:33           ` Grant Coady
2005-08-04  7:44           ` Rolf Eike Beer
2005-08-05 22:52         ` Jesper Juhl
2005-08-03 21:46       ` Bodo Eggert
2005-08-03 23:19         ` Jesper Juhl [this message]
2005-08-03 11:50 ` Pavel Machek

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=200508040119.20289.jesper.juhl@gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=7eggert@gmx.de \
    --cc=akpm@osdl.org \
    --cc=dmlb2000@gmail.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=gene.heskett@verizon.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=richard.hubbell@gmail.com \
    --cc=rlrevell@joe-job.com \
    --cc=rostedt@goodmis.org \
    --cc=sean.bruno@dsl-only.net \
    --cc=torvalds@osdl.org \
    --cc=vyas.puneet@gmail.com \
    --cc=webmaster@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