Re: what mailing list to follow (for gcc-gfortran ?)

Re: what mailing list to follow (for gcc-gfortran ?)

[Joost VandeVondele]

> What is the mailing list one needs to follow for further gfortran
> development?  I've scanned the gcc@gc... list archive
> and discovered several gfortran posts that were not posted to
> the gcc-g95-devel list.  I suspect that 98% of the posts to gcc@

gcc@gcc is related to inlining in C++ if I understand correctly ;)

> are not related to gfortran, so tracking this list is somewhat
> inefficient.

and should f90 bugs be mailed to

gcc-g95-devel@lists.sourceforge.net

or should they go in bugzilla ?

Joost

RE: what mailing list to follow (for gcc-gfortran ?)

[Gerald Pfeifer]

On Tue, 5 Aug 2003, S. Bosscher wrote:
> Until we've figured out if/when we can get our own @gcc mailing list, I'd
> very much prefer that _everything_ related only to gfortran just stays on
> the gcc-g95 list.  Including patches.

You can definitely have your "own" @gcc mailing list right away.  Just
discuss with Toon, mostly, how to call that list and have Toon send mail
to overseers@gcc.gnu.org and that's it.

On Tue, 5 Aug 2003, Joseph S. Myers wrote:
> Do you want a gfortran-cvs mailing list, to receive that subset of gcc-cvs
> messages, in addition to them going to gcc-cvs?  If so, web archived (as
> with libstdc++-cvs) or not (as with java-cvs)?
>
> Do you want separate discussion and patches lists (as with Java) or just
> one list for both (as with libstdc++)?

My suggestion is to start with a $SOMENAME@gcc.gnu.org list where you
have both patches and general discussions and split that list whenever
you deem useful.

If you think a $SOMENAME-cvs@gcc.gnu.org list is useful to have, that
should be easy to set up as well.

Gerald

RE: what mailing list to follow (for gcc-gfortran ?)

[Joseph S. Myers]

On Tue, 5 Aug 2003, S. Bosscher wrote:

> Until we've figured out if/when we can get our own @gcc mailing list, I'd
> very much prefer that _everything_ related only to gfortran just stays on
> the gcc-g95 list.  Including patches.

You need to make several choices about what lists are wanted, following
which features of those presently used for subprojects.

Do you want a gfortran-cvs mailing list, to receive that subset of gcc-cvs 
messages, in addition to them going to gcc-cvs?  If so, web archived (as 
with libstdc++-cvs) or not (as with java-cvs)?

Do you want separate discussion and patches lists (as with Java) or just
one list for both (as with libstdc++)?

Should patches to the runtime library (and discussion thereof) go to
gcc-patches as well as gfortran/gfortran-patches?  For libstdc++ they go
to both.  For Java, front end patches go to both (and I think this at
least should be kept for gfortran) while libgcj patches go only to
java-patches.

[Note that these patch policies are documented in both lists.html and
contribute.html.  We might want to do something about this duplication.]

Do you want a list to receive gfortran bug reports and discussion thereof
(which of course would also go to gcc-bugs)?  The Java maintainers have
recently requested the return of the list they had for this purpose
<http://gcc.gnu.org/ml/gcc/2003-08/msg00008.html>.

-- 
Joseph S. Myers
jsm@polyomino.org.uk

RE: what mailing list to follow (for gcc-gfortran ?)

[S. Bosscher]

Until we've figured out if/when we can get our own @gcc mailing list, I'd
very much prefer that _everything_ related only to gfortran just stays on
the gcc-g95 list.  Including patches.

Thanks,

Gr.
Steven



-----Original Message-----
From: Joost VandeVondele
To: gcc-g95-devel@lists.sourceforge.net
Cc: gcc@gcc.gnu.org
Sent: 5-8-03 8:58
Subject: Re: what mailing list to follow (for gcc-gfortran ?)

> What is the mailing list one needs to follow for further gfortran
> development?  I've scanned the gcc@gc... list archive
> and discovered several gfortran posts that were not posted to
> the gcc-g95-devel list.  I suspect that 98% of the posts to gcc@

gcc@gcc is related to inlining in C++ if I understand correctly ;)

> are not related to gfortran, so tracking this list is somewhat
> inefficient.

and should f90 bugs be mailed to

gcc-g95-devel@lists.sourceforge.net

or should they go in bugzilla ?

Joost