[cp-patches] FYI: Update hacking Branches rules

[Mark Wielaard]

Hi,

I installed this documentation update that we discussed on the main
list.

2005-12-13  Mark Wielaard  <address@hidden>

    * doc/hacking.texinfo (Branches): Explain "broken" branches a bit
    more.

Committed,

Mark

Index: doc/hacking.texinfo
===================================================================
RCS file: /cvsroot/classpath/classpath/doc/hacking.texinfo,v
retrieving revision 1.39
diff -u -r1.39 hacking.texinfo
--- doc/hacking.texinfo 11 Dec 2005 21:55:08 -0000      1.39
+++ doc/hacking.texinfo 13 Dec 2005 10:12:32 -0000
@@ -848,11 +848,13 @@
 @item Requirements for patch email to classpath-patches and for paperwork
 @strong{cannot} be lifted. See @ref{Requirements}.
 
address@hidden A branch should not see it as ``private'' or
-``may be broken at random times''. It should be as much as possible
address@hidden A branch should not be seen as ``private'' or
+``may be completely broken''. It should be as much as possible
 something that you work on with a team (and if there is no team - yet
 - then there is nothing as bad as having a completely broken build to
-get others to help out).
+get others to help out). There can of course be occasional breakage, but
+it should be planned and explained. And you can certainly have a rule
+like ``please ask me before committing to this branch''.
 
 @item Merges from the trunk to a branch are at the discretion of the
 branch maintainer.

signature.asc
Description: This is a digitally signed message part