From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: http://sourceware.org/gettext/ abandoned
Date: Thu, 14 Jan 2010 16:54:00 -0000 [thread overview]
Message-ID: <20100114165432.GH9964@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20100114164823.GE9964@ednor.casa.cgf.cx>
On Thu, Jan 14, 2010 at 11:48:24AM -0500, Christopher Faylor wrote:
>On Sat, Jan 02, 2010 at 04:19:29PM +0100, Gerald Pfeifer wrote:
>>On Sat, 24 Oct 2009, Christopher Faylor wrote:
>>>> If there's another (current) website for the same project, permanent
>>>> HTTP redirects to the current site seem the best approach. I only see
>>>> a single page on the http://sourceware.org/gettext/ site so redirecting
>>>> to http://www.gnu.org/software/gettext/ should be very easy.
>>> Agreed. Keeping an obsolete site active for nebulous archival purposes
>>> is not helping anyone.
>>>
>>> I don't see any reason to keep an archive around either. If this is
>>> really important, I'll bet most of this stuff is already archived at
>>> archive.org.
>>
>>Somehow http://sourceware.org/gettext/ still is "active", though. Was
>>anyone going to add the redirect? If not, I can certainly give it a try.
>
>Many months later: I've finally gotten around to this. Attempts to
>access http://sourceware.org/gettext will be redirected to
>http://sourceware.org/gettext .
http://www.gnu.org/software/gettext/
cgf
prev parent reply other threads:[~2010-01-14 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 12:31 Gerald Pfeifer
2009-10-10 15:09 ` Christopher Faylor
2009-10-23 14:12 ` Jonathan Larmour
2009-10-23 16:37 ` Frank Ch. Eigler
2009-10-23 17:52 ` Joseph S. Myers
2009-10-24 14:47 ` Christopher Faylor
2010-01-02 15:19 ` Gerald Pfeifer
2010-01-14 16:48 ` Christopher Faylor
2010-01-14 16:54 ` Christopher Faylor [this message]
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=20100114165432.GH9964@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=gerald@pfeifer.com \
--cc=overseers@sourceware.org \
/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).