Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Thiemo Seufer <ths@networkno.de>
Cc: 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:40:00 -0000	[thread overview]
Message-ID: <17799.2500.313634.850705@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061218210934.GB17301@networkno.de>

Thiemo Seufer writes:
 > Daniel Jacobowitz wrote:
 > > On Mon, Dec 18, 2006 at 03:16:48PM +0400, Joel Brobecker wrote:
 > > > Hello,
 > > > 
 > > > I noticed that we are still refering to sources.redhat.com in the GDB
 > > > web pages. Shouldn't we be using sourceware.org instead? I can make
 > > > the change in the HTML, but I want to make sure it is desired first.
 > > 
 > > Yes, please do!
 > 
 > FWIW, CONTRIBUTE also still mentions gdb-patches@sources.redhat.com.

Unless I'm missing the point and the servers have already moved:

If Red Hat decide that they no longer want to host the GDB website/repository/
mailing lists will there be someone ready to step in and fill their place?  I,
for one, appreciate the superior hosting service that they provide over GNU
servers which are slower and generally less reliable.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2006-12-18 21:40 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 [this message]
2006-12-18 21:42       ` Daniel Jacobowitz
2006-12-18 21:59         ` Nick Roberts
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.2500.313634.850705@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=brobecker@adacore.com \
    --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