From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: overseers@sourceware.org, Thomas Schwinge <thomas@schwinge.name>
Subject: Re: Shell access / mailing list mbox archives
Date: Sat, 02 Apr 2011 21:49:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1104022149000.20060@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1104022315080.6055@gerinyyl>
On Sat, 2 Apr 2011, Gerald Pfeifer wrote:
> On Fri, 1 Apr 2011, Thomas Schwinge wrote:
> >> I'd like to get access to the mbox archives for sourceware.org /
> >> gcc.gnu.org mailing list archives.
> > No answer, so I take it this is not admissible. To get what I'd like, I
> > shall have to write some scripting hackery for interfacing with ezmlm by
> > email -- luckily this is ezmlm-idx, which allows for obtaining for ``a
> > maximum of 100 [messages] per request''. Yet, given the list archives'
> > sizes, this will be some thousand request / answer emails, several
> > hundred MiB worth of data to transfer; to which timeframe should I
> > spread my requests to not needlessly stress the poor sourceware.org
> > machine?
>
> Is there a more direct way to provide to Thomas what he wants? I
> could not find any mbox files on gcc.gnu.org any more, but perhaps
> I've been missing them somewhere (or the could be recreated easily)?
They're /sourceware/vault/old-ftp-archives/.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-04-02 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 22:46 Thomas Schwinge
2011-04-01 21:01 ` Thomas Schwinge
2011-04-01 22:12 ` Christopher Faylor
2011-04-02 21:16 ` Gerald Pfeifer
2011-04-02 21:49 ` Joseph S. Myers [this message]
2011-04-02 21:57 ` Gerald Pfeifer
2011-04-03 3:46 ` Ian Lance Taylor
2011-04-03 20:38 ` Thomas Schwinge
2011-04-03 20:59 ` Gerald Pfeifer
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.1104022149000.20060@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gerald@pfeifer.com \
--cc=overseers@sourceware.org \
--cc=thomas@schwinge.name \
/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).