I don't think it makes sense to have all the kernel sources ever in one
giant CVS tree. Start fresh with 2.0, create a branch for 2.1.
> better yet, tell us that were twits and someone else is already doing it
> and we don't have to :)
>
Quite a few people have their kernel in their own CVS tree. Unfortunately,
CVS cannot do distributed repositories (i.e. have a local repository that
branches off a remote one). Thus, there's no good way to actually check /
version control your changes. :-(
There are a bunch of not-so-good-ways, of course. Since CVS has a few other
problems, the best way would probably be to implement a _real_ distributed
file version manager... one with free source code.
-- I got a garage door opener. It can't close. Just open. -- Steve Wright-- Matthias Urlichs \ noris network GmbH / Xlink-POP Nürnberg Schleiermacherstraße 12 \ Linux+Internet / EMail: urlichs@noris.de 90491 Nürnberg (Germany) \ Consulting+Programming+Networking+etc'ing PGP: 1024/4F578875 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE Click <A HREF="http://info.noris.de/~smurf/finger">here</A>. 42