This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

wwwdocs PATCH for Re: PATCH for Re: ObjC improvements and ObjC++


On Thu, 10 Jul 2003, Ziemowit Laski wrote:
> Well, here's what I did that seemed to work correctly (appropriately
> parameterized):
>
>    cvs -d :ext:$USER@gcc.gnu.org:/cvs/gcc rtag $BRANCH-branchpoint gcc
>    cvs -d :ext:$USER@gcc.gnu.org:/cvs/gcc rtag -b -r $BRANCH-branchpoint
> $BRANCH-branch gcc
>
> As I described previously, using plain old 'cvs tag' against a working
> copy seemed flaky, possibly due to flakiness in 'cvs checkout' itself.
> This is a bit frightening, actually, and I hope someone will look into
> it.

As promised, I now installed the patch below based on your details.

Thanks!
Gerald

Index: cvswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvswrite.html,v
retrieving revision 1.57
diff -u -3 -p -r1.57 cvswrite.html
--- cvswrite.html	10 Jul 2003 17:24:16 -0000	1.57
+++ cvswrite.html	14 Jul 2003 12:05:37 -0000
@@ -400,7 +400,14 @@ done
 <h2><a name="branches">Creating branches</a></h2>

 <p>When creating a branch for development, you should first tag the
-branchpoint. Also, please document such branches at
+branchpoint, for example as follows:</p>
+
+<blockquote><pre>
+cvs rtag $BRANCH-branchpoint gcc
+cvs rtag -b -r $BRANCH-branchpoint $BRANCH-branch gcc
+</pre></blockquote>
+
+<p>Also, please document such branches at
 <a href="cvs.html#devbranches">cvs.html#devbranches</a>.
 </p>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]