public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Where do I mention a branch in our web pages?
@ 2004-08-12 20:59 Mark Mitchell
  2004-08-13 19:26 ` Gerald Pfeifer
  0 siblings, 1 reply; 5+ messages in thread
From: Mark Mitchell @ 2004-08-12 20:59 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc

Gerald --

I've created a csl-3_3_1-branch for some support work we'll be doing for 
a version of GCC based off of 3.3.1.  It's probably not going to be 
interested to anyone except our direct customers, but I wanted to be a 
good citizen and put in on the web pages.  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?

Thanks,

-- 
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Where do I mention a branch in our web pages?
  2004-08-12 20:59 Where do I mention a branch in our web pages? Mark Mitchell
@ 2004-08-13 19:26 ` Gerald Pfeifer
  2004-08-13 21:45   ` Joe Buck
  2004-08-15 19:43   ` Mark Mitchell
  0 siblings, 2 replies; 5+ messages in thread
From: Gerald Pfeifer @ 2004-08-13 19:26 UTC (permalink / raw)
  To: Mark Mitchell; +Cc: gcc, Jeffrey A Law

On Thu, 12 Aug 2004, Mark Mitchell wrote:
> I've created a csl-3_3_1-branch for some support work we'll be doing for a 
> version of GCC based off of 3.3.1.  It's probably not going to be interested 
> to anyone except our direct customers, but I wanted to be a good citizen and 
> put in on the web pages.

Which definitely is a good thing, thanks!

> 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?

Gerald

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Where do I mention a branch in our web pages?
  2004-08-13 19:26 ` Gerald Pfeifer
@ 2004-08-13 21:45   ` Joe Buck
  2004-08-14 14:10     ` Kai Henningsen
  2004-08-15 19:43   ` Mark Mitchell
  1 sibling, 1 reply; 5+ messages in thread
From: Joe Buck @ 2004-08-13 21:45 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: Mark Mitchell, gcc, Jeffrey A Law

On Fri, Aug 13, 2004 at 09:19:08PM +0200, Gerald Pfeifer wrote:
> 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?

I'm not entirely sure that Vendor is the right word here, and I'm not sure
what such branches should be called (suggestions welcome).  I would like
to see them listed somehow.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Where do I mention a branch in our web pages?
  2004-08-13 21:45   ` Joe Buck
@ 2004-08-14 14:10     ` Kai Henningsen
  0 siblings, 0 replies; 5+ messages in thread
From: Kai Henningsen @ 2004-08-14 14:10 UTC (permalink / raw)
  To: gcc

Joe.Buck@synopsys.COM (Joe Buck)  wrote on 13.08.04 in <20040813142857.A15736@synopsys.com>:

> On Fri, Aug 13, 2004 at 09:19:08PM +0200, Gerald Pfeifer wrote:
> > 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?
>
> I'm not entirely sure that Vendor is the right word here, and I'm not sure
> what such branches should be called (suggestions welcome).  I would like
> to see them listed somehow.

Anything I came up with was worse, such as "Packager branches" ...

MfG Kai

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Where do I mention a branch in our web pages?
  2004-08-13 19:26 ` Gerald Pfeifer
  2004-08-13 21:45   ` Joe Buck
@ 2004-08-15 19:43   ` Mark Mitchell
  1 sibling, 0 replies; 5+ messages in thread
From: Mark Mitchell @ 2004-08-15 19:43 UTC (permalink / raw)
  To: Gerald Pfeifer; +Cc: gcc, gcc-patches, Jeffrey A Law

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

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


[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1070 bytes --]

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 />

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-08-15 19:36 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-12 20:59 Where do I mention a branch in our web pages? Mark Mitchell
2004-08-13 19:26 ` Gerald Pfeifer
2004-08-13 21:45   ` Joe Buck
2004-08-14 14:10     ` Kai Henningsen
2004-08-15 19:43   ` Mark Mitchell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).