gomp-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gomp-discuss] CVS?


From: Diego Novillo
Subject: Re: [Gomp-discuss] CVS?
Date: Wed, 13 Oct 2004 12:19:11 -0400

On Wed, 2004-10-13 at 11:50, Scott Robert Ladd wrote:

> It is not listed on the official GCC web site:
> 
>       http://gcc.gnu.org/cvs.html
> 
> In fact, the only branch listed there for gomp is "inactive".
> 
Remember that I had submitted a patch for it and jsm/gerald had
suggested changes?  At the time I asked you if you would volunteer to
make them.  I think we just crossed our wires and I dropped the ball :)
Apologies.


> Should I also submit a patch to the above page, linking to the other 
> page I wrote?
>
Yes.  The idea is for cvs.html contain a brief description of the branch
and a link to the project's page.  Here's what we could use.  If you
want to submit all of it together, replace "GOMP project" with a link to
the new project web page that you created.


Index: cvs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.156
diff -d -u -p -r1.156 cvs.html
--- cvs.html    6 Oct 2004 01:50:26 -0000       1.156
+++ cvs.html    13 Oct 2004 16:18:34 -0000
@@ -227,6 +227,15 @@ particular releases or snapshots or the
   contribution and testing rules apply.  Patches should be CC'd
   to Daniel Berlin for final approval.</dd>

+  <dt>gomp-branch</dt>
+  <dd>This branch is used by the GOMP project to implement <a
+  href="http://www.openmp.org/";>OpenMP</a> support in GCC.
+  Patches and discussions regarding the design and implementation
+  of GOMP should go to the main GCC development lists.  Messages
+  should be marked with <code>[gomp]</code> in the subject line.
+  The usual contribution and testing rules apply.  The branch is
+  maintained by Diego Novillo and Sebastian Pop.  Patches should
+  be approved by the respective maintainers.</dd>
 </dl>

 <h4>Architecture-specific</h4>






reply via email to

[Prev in Thread] Current Thread [Next in Thread]