CVS on sourceforge

[<fp...@zu...>]

I propose the following stategy to handle the CVS repository on sourceforge:

The trunk always contains the most recent "official" source tree of
the entire APUS kernel source.

When somebody wishes to make patches, (s)he creates a branch and makes
the changes there. After checkin, we can have a peer review, and if
it is found good, it is merged with the trunk, creating a new release.
Using this, we do not have to "pollute" the mailing list with diffs.

Another option would be to have the tunk as the official Linus kernel, and
the stuff proposed above as a branch.

And, we should define some naming policy for tags.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.