From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Thiemo Seufer <ths@networkno.de>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC/www] Replace sources.redhat.com by sourceware.org?
Date: Mon, 18 Dec 2006 21:59:00 -0000 [thread overview]
Message-ID: <17799.3609.477777.401115@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061218214233.GA22449@nevyn.them.org>
> It has nothing to do with the hosting, which hasn't changed; we were
> asked (by the FSF I think) not to use the sources.redhat.com name
> when talking about the GNU projects. It's supposed to be updated
> to point to sourceware.org, which is the same.
If everyone is agreeable then I guess there's no problem.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-12-18 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 11:16 Joel Brobecker
2006-12-18 13:38 ` Daniel Jacobowitz
2006-12-18 21:23 ` Thiemo Seufer
2006-12-18 21:40 ` Nick Roberts
2006-12-18 21:42 ` Daniel Jacobowitz
2006-12-18 21:59 ` Nick Roberts [this message]
2007-01-04 20:29 ` Daniel Jacobowitz
2006-12-20 5:36 ` [commit/www] Replaced sources.redhat.com with sourceware.org Joel Brobecker
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=17799.3609.477777.401115@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=ths@networkno.de \
/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