From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Akula2 <akula2.shark@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Jumping into Kernel development: About -rc kernels...
Date: Tue, 09 Jan 2007 19:08:57 +0100 [thread overview]
Message-ID: <45A3DA39.70604@s5r6.in-berlin.de> (raw)
In-Reply-To: <8355959a0701090733l74d03792q16b3022d949c7ae1@mail.gmail.com>
Akula2 wrote:
> Should I start compile/test/debug one-after-one in this fashion:-
>
> 2.6.19 source + patch-2.6.20-rc1
> 2.6.19 source + patch-2.6.20-rc2
> 2.6.19 source + patch-2.6.20-rc3
> 2.6.19 source + patch-2.6.20-rc4
Or
linux-2.6.19 + testing/patch-2.6.20-rc1 = linux-2.6.20-rc1
linux-2.6.20-rc1 + testing/incr/patch-2.6.20-rc1-rc2 = linux-2.6.20-rc2
linux-2.6.20-rc2 + testing/incr/patch-2.6.20-rc2-rc3 = linux-2.6.20-rc3
and so on.
> OR
>
> Pick the latest release number?
Or this. Or use git as was suggested by others, to track kernel changes
in a finer-grained manner. Or try the -mm patchset which has --- how
shall I call it --- pre-release code. Or track some subsystem-specific
or architecture-specific development trees if you are especially
interested in a platform or driver subsystem. See the MAINTAINERS file
for their development repositories. These repos do not always carry
self-contained source trees though, and what purposes they serve for the
maintainers and how they can be used by others than the maintainers
differs from repo to repo.
--
Stefan Richter
-=====-=-=== ---= -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-01-09 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 15:33 Akula2
2007-01-09 15:49 ` Jesper Juhl
2007-01-09 21:04 ` Akula2
2007-01-09 16:23 ` Horst H. von Brand
2007-01-09 18:08 ` Stefan Richter [this message]
[not found] <20070110150051.63974.qmail@web15914.mail.cnb.yahoo.com>
2007-01-10 18:07 ` Stefan Richter
2007-01-10 20:05 ` Paolo Ornati
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=45A3DA39.70604@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akula2.shark@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
all inboxes | Powered by JetHome®