From: Mark Mitchell <mark@codesourcery.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Zack Weinberg <zack@codesourcery.com>,
Joe Buck <jbuck@synopsys.com>, DJ Delorie <dj@delorie.com>,
aoliva@redhat.com, cgf@redhat.com, gcc@gcc.gnu.org,
binutils@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Updating to Autoconf 2.5x
Date: Tue, 10 Jun 2003 15:57:00 -0000 [thread overview]
Message-ID: <1055260613.9414.38.camel@doubledemon.codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0306101022100.6442@kern.srcf.societies.cam.ac.uk>
On Tue, 2003-06-10 at 02:25, Joseph S. Myers wrote:
> On Tue, 9 Jun 2003, Mark Mitchell wrote:
>
> > [However, I do think it's odd that the FSF worked so hard to get GCC to
> > come from gcc.gnu.org, but binutils and lots of other GNU stuff still
> > comes from sources.redhat.com.]
>
> But the binutils@gcc.gnu.org alias for the list was set up on 18 Jun 2001
> in response to a request from RMS. (I don't know about GDB, or about the
> FSF position on which domain name is used in documentation. overseers
> likewise has a list alias @gcc.gnu.org.)
That's all well and good, but the basic point certainly remains: we've
worked very hard to make GCC appear to come entirely from a machine
named gcc.gnu.org, and similar work has not been done for GDB, binutils,
glibc, etc. Red Hat domain names and logos appear frequently on those
web pages.
Frankly, I don't think this matters nearly as much as it might have in
the past; the world has gotten a lot more savvy about GNU software and
people don't seem to get confused about some company "owning" it nearly
as often.
I don't object to a policy that gnu.org domains ought to be used even
for transient GCC mailing lists. But then we should be actively trying
to set up {binutils,gdb,glibc}.gnu.org and/or sources.gnu.org; the use
of sources.redhat.com for those projects creates much more potential for
confusion. A first step would be do separate the sources.redhat.com
site into a site for GNU project programs and non-GNU project programs;
GDB would go on the first site, while Cygwin and Red Boot would go on
the other.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next prev parent reply other threads:[~2003-06-10 15:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 20:32 Zack Weinberg
2003-06-09 21:05 ` Andrew Cagney
2003-06-09 21:09 ` Christopher Faylor
2003-06-09 22:58 ` Alexandre Oliva
2003-06-09 23:06 ` Daniel Jacobowitz
2003-06-09 23:38 ` Joe Buck
2003-06-09 23:48 ` DJ Delorie
2003-06-10 0:33 ` Joe Buck
2003-06-10 4:40 ` Zack Weinberg
2003-06-10 6:42 ` Mark Mitchell
2003-06-10 9:25 ` Joseph S. Myers
2003-06-10 14:24 ` Christopher Faylor
2003-06-10 15:57 ` Mark Mitchell [this message]
2003-06-10 16:40 ` Christopher Faylor
2003-06-12 4:16 ` Red Hat logos on FSF web pages (was Re: Updating to Autoconf 2.5x) Christopher Faylor
2003-06-10 17:40 ` Updating to Autoconf 2.5x Andrew Cagney
2003-06-10 13:48 ` Kaveh R. Ghazi
2003-06-10 14:23 ` Christopher Faylor
2003-06-10 14:30 ` Daniel Jacobowitz
2003-06-10 15:44 ` Andrew Cagney
2003-06-10 16:03 ` Mark Mitchell
2003-06-10 17:47 ` Joe Buck
2003-06-09 23:58 ` Daniel Jacobowitz
2003-06-10 0:50 ` Alexandre Oliva
2003-06-10 0:55 ` DJ Delorie
2003-06-10 2:58 ` Christopher Faylor
2003-06-10 3:43 ` Ian Lance Taylor
2003-06-10 2:37 ` Christopher Faylor, Christopher Faylor
2003-06-09 21:15 ` DJ Delorie
2003-06-09 23:01 ` Zack Weinberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1055260613.9414.38.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=binutils@gcc.gnu.org \
--cc=cgf@redhat.com \
--cc=dj@delorie.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jbuck@synopsys.com \
--cc=jsm28@cam.ac.uk \
--cc=zack@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).