linux-kernel - Re: Jumping into Kernel development: About -rc kernels...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45A3DA39.70604@s5r6.in-berlin.de>
Date:	Tue, 09 Jan 2007 19:08:57 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Akula2 <akula2.shark@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Jumping into Kernel development: About -rc kernels...

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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/