Ok, which branch/tag do I use for egcs 1.1.2?

Dave Love d.love@dl.ac.uk
Thu Feb 25 09:55:00 GMT 1999


>>>>> "JCB" == Craig Burley <craig@jcb-sc.com> writes:

 JCB> I'd like to fix the g77 docs for egcs 1.1.2, but the previous
 JCB> patches I put in the egcs_1_1_branch (a couple of which could
 JCB> use Dave Love's fixing anyway)

Not sure what that means.

 JCB> aren't in the egcs_1_1_2_prerelease_2 branch/tag.  I guess
 JCB> they're down a black hole, save for the fact I put them on the
 JCB> mainline as well.

I could merge specified missing changes from the mainline if
appropriate, though the notwork isn't at its best just now.

 JCB> Presumably I've missed a memo or something, so pointers to the
 JCB> appropriate info would be appreciated!

The cvs instructions might as well be updated.  Do they need more
explanation, though?

Index: cvs.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.16
diff -u -p -r1.16 cvs.html
--- cvs.html	1999/02/16 06:54:51	1.16
+++ cvs.html	1999/02/25 17:16:20
@@ -69,17 +69,20 @@ FAQ entry regarding additional tools</a>
 FAQ entry documents <a href="faq.html#gperf">changes you will likely have
 to make to the gperf utility</a>.
 
-<p> You can check out the egcs-1.0.x release branch with the following command:
+<h3>CVS tags and checkouts</h3>
 
-<pre>	cvs -z 9 co -regcs_1_00_branch egcs</pre>
+<p> You can check out the latest version of the egcs-1.1.x release
+branch with the following command:
 
+<pre>	cvs -z 9 co -regcs_1_1_branch egcs</pre>
+
 <p>By changing the <code>"-r"</code> argument above you can check out
 particular releases or snapshots or the latest snapshot.
 
 <ul>
-  <li> egcs_1_0_2_release
-  <li> egcs_1_0_1_release
-  <li> egcs_1_0_release
+  <li> egcs_1_1_2_release
+  <li> egcs_1_1_1_release
+  <li> egcs_1_1_release
   <li> egcs_ss_yymmdd
   <li> egcs_latest_snapshot
 </ul>


More information about the Gcc-patches mailing list