From: Ian Lance Taylor <ian@wasabisystems.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: Archive bug-binutils?
Date: Thu, 15 Jan 2004 18:20:00 -0000 [thread overview]
Message-ID: <m3wu7tm5ty.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040115181709.GA16598@redhat.com>
Christopher Faylor <cgf@redhat.com> writes:
> On Thu, Jan 15, 2004 at 12:54:56PM -0500, Ian Lance Taylor wrote:
> >I could probably figure this out, but maybe somebody knows the answer
> >off the top of their head. The bug-binutils@gnu.org mailing list is
> >now working properly--we have activated spam blocking, and are using
> >moderators to eliminate the remaining spam. I would like to reactive
> >the archive which is accessible from sourceware.org (it currently says
> >that there were no messages from January to March, which I know is
> >untrue). How should I do this?
>
> Why do you want to do this? AFAIK, bug-binutils is already archived
> at gnu.org. Why duplicate the archive? I've never understood why
> we are archiving mail from other mailing lists on sourceware.org.
> If it is crucial that we access the archive from sourceware.org,
> couldn't we just set up a link?
Hmmm, I was thinking that it would be nice to have the same archive
format as all the other sourceware lists. But perhaps you are right.
I'll just put a link to the bug-binutils archive from the binutils web
page.
Ian
next prev parent reply other threads:[~2004-01-15 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 17:55 Ian Lance Taylor
2004-01-15 18:17 ` Christopher Faylor
2004-01-15 18:20 ` Ian Lance Taylor [this message]
2004-01-15 18:27 ` Christopher Faylor
2004-01-15 18:30 ` Ian Lance Taylor
2004-01-15 20:41 ` Angela Marie Thomas
2004-01-15 21:04 ` Christopher Faylor
2004-01-15 21:15 ` Angela Marie Thomas
2004-01-16 0:45 ` Jonathan Larmour
2004-01-16 3:40 ` Alexandre Oliva
2004-01-16 1:05 ` Phil Edwards
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=m3wu7tm5ty.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=cgf@redhat.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).