public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@actcom.co.il>
To: Russ Fink <russfink@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: structure of ftp.kernel.org, patch dirs
Date: Wed, 24 Apr 2002 09:27:45 +0300	[thread overview]
Message-ID: <20020424092745.H22237@actcom.co.il> (raw)
In-Reply-To: <F43O6Nr85kNScMZ3lVR00008888@hotmail.com>

On Thu, Apr 18, 2002 at 01:10:29PM -0400, Russ Fink wrote:
> Hello,
> 
> I'm a linux vet, but am relatively new to kernel compiling.  I'm trying to 
> trace a nasty bug, and I wish to build incremental kernels of the 2.2 tree. 
> I'm looking at ftp.kernel.org in the v2.2/testing directory, and have a 
> question about the directory setup.
> 
> Can someone tell me, what is the difference between patches in the "incr" 
> directory and patches in the "old" directory?
> 
> In pub/linux/kernel/v2.2/testing/incr/ I see files such as:
> patch-2.2.19-pre1-pre2.gz

That would be the patch that is the diff between 2.2.19-pre1 and
2.2.19-pre2. If you already have a tree with 2.2.19-pre1, you could
apply this patch and get a tree which is 2.2.19-pre2. 

> whereas in pub/linux/kernel/v2.2/testing/old/ I see:
> patch-2.2.19-pre2.gz

That would be a patch between 2.2.19 and 2.2.19-pre2. If you had a
pristine tree with 2.2.19, you would apply this one and get a tree
with 2.2.19-pre2. 

> My objective is to start with the latest 2.2.17 sources and patch it up to 
> specific levels, e.g., 2.2.18-pre3.  Do I use patches in "incr", or patches 
> in "old"?

If you want to go 17->18-prex directly, use the specific patch in
'old'. If you want to go through each pre in order, use those in
'incr'. 

> I'm guessing that "old" patches will take me from 2.2.17 to version
> 2.2.18-pre-"N" without needing to go through the previous N-1 patches first, 
> but that patches in "incr" will only take me from one patch level to the 
> next higher level (from 1 to 2, etc).  They appear to be smaller patch 
> files.  Is this right?

Sounds so. 
-- 
The ill-formed Orange
Fails to satisfy the eye:       http://vipe.technion.ac.il/~mulix/
Segmentation fault.             http://syscalltrack.sf.net/

      reply	other threads:[~2002-04-24  6:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 17:10 structure of ftp.kernel.org, patch dirs Russ Fink
2002-04-24  6:27 ` Muli Ben-Yehuda [this message]

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=20020424092745.H22237@actcom.co.il \
    --to=mulix@actcom.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=russfink@hotmail.com \
    /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