From: "Russ Fink" <russfink@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: structure of ftp.kernel.org, patch dirs
Date: Thu, 18 Apr 2002 13:10:29 -0400 [thread overview]
Message-ID: <F43O6Nr85kNScMZ3lVR00008888@hotmail.com> (raw)
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
whereas in pub/linux/kernel/v2.2/testing/old/ I see:
patch-2.2.19-pre2.gz
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"?
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?
Thanks for your time,
Russ Fink
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
next reply other threads:[~2002-04-24 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 17:10 Russ Fink [this message]
2002-04-24 6:27 ` Muli Ben-Yehuda
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=F43O6Nr85kNScMZ3lVR00008888@hotmail.com \
--to=russfink@hotmail.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
all inboxes | Powered by JetHome®