This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Where do I mention a branch in our web pages?
Gerald Pfeifer wrote:
I can't figure out where to put it, though; it doesn't really fit in
the categories here:
http://gcc.gnu.org/cvs.html
It's more like the Red Hat release branches than anything else, and I
don't see them there either. What's the policy for such a branch?
I don't think we have clearly documented such a policy so far, but I do
agree that we should, indeed, also list such branches.
How about creating a new section to cvs.html, called "Vendor Branches"
for example, and documenting your branch there? Jeff, what do you think?
Would you mind adding the rh- branches there as well?
Here is what I committed.
I used the less-controversial term "Distributor" in lieu of "Vendor".
Let me know if there are any problems with that.
Thanks,
--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com
Index: cvs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.148
diff -c -5 -p -r1.148 cvs.html
*** cvs.html 21 Jul 2004 00:14:13 -0000 1.148
--- cvs.html 15 Aug 2004 19:34:59 -0000
*************** particular releases or snapshots or the
*** 295,304 ****
--- 295,318 ----
maintained by Andrew Haley. Patches should be marked with the
tag <code>[BC ABI]</code> in the subject line.</dd>
</dl>
+ <h3><a name="distrobranches">Distribution Branches</a></h3>
+
+ <p>These branches are maintained by organizations distributing GCC.
+ No changes should be made to those branches without the explicit
+ permission of the distributing organization. The branch name should
+ be prefixed with the initials of the distributing organization.</p>
+
+ <dl>
+
+ <dt>csl-3_3_1-branch</dt>
+ <dd>CodeSourcery release based on GCC 3.3.1.</dd>
+
+ </dl>
+
<h3><a name="olddevbranches">Inactive Development Branches</a></h3>
<dl>
<dt>cp-parser-branch<br />