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]

Re: [wwwdocs] Update status of gomp-branch

From: Diego Novillo <dnovillo at redhat dot com>
To: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Date: Tue, 07 Sep 2004 20:45:50 -0400
Subject: Re: [wwwdocs] Update status of gomp-branch
Organization: Red Hat Canada
References: <1094581255.21733.82.camel@localhost.localdomain> <Pine.LNX.4.61.0409072347420.4882@digraph.polyomino.org.uk>

On Tue, 2004-09-07 at 20:00, Joseph S. Myers wrote:

> You seem to be editing the entry in the "Inactive Development Branches" 
> section.  Shouldn't gomp-01-branch stay there as an inactive branch, with 
> a new entry as an active branch for the new branch?
> 
Good point.  I'll rearrange the entries.

> In addition to commit policies it would also be a good idea to have some 
> indication of where discussions relating to the branch go - which, if it 
> is intended for possible merge to mainline, should include the main gcc 
> list for any matters of design of relevance to the rest of the compiler.
>
Yes.  There is an external list, but all contributions to the branch
will have to follow FSF guidelines and discussion relating the project
will happen on gcc/gcc-patches.


Diego.

References:
- [wwwdocs] Update status of gomp-branch
  - From: Diego Novillo
- Re: [wwwdocs] Update status of gomp-branch
  - From: Joseph S. Myers

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