From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sourceware.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: http://sourceware.org/gettext/ abandoned
Date: Fri, 23 Oct 2009 17:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0910231750300.22518@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20091023163725.GA2995@redhat.com>
On Fri, 23 Oct 2009, Frank Ch. Eigler wrote:
> Hi -
>
> On Sat, Oct 10, 2009 at 11:09:10AM -0400, Christopher Faylor wrote:
> > [...]
> > >How do we usually handle such a case?
> >
> > I think I usually say "I'd like to delete this" and someone says "Oh no!
> > There are still people in Albania who rely on this web site for their
> > sole survival! If you delete it, thousands will perish!!!!" [...]
>
> If the costs of keeping this stuff online are in the noise, let's keep
> it archived on line, being in a small way curators of history. (If
> they crowd with the projects-list web page, then let's move them
> somewhere down the list.)
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-10-23 17:52 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 [this message]
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
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=Pine.LNX.4.64.0910231750300.22518@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fche@redhat.com \
--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).