public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@schwinge.name>
To: overseers@sourceware.org
Subject: Shell access / mailing list mbox archives
Date: Mon, 07 Feb 2011 22:46:00 -0000	[thread overview]
Message-ID: <878vxra2gl.fsf@kepler.schwinge.homeip.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]

Hallo!

I'd like to get access to the mbox archives for sourceware.org /
gcc.gnu.org mailing list archives.  For some years, I've been subscribed
to a bunch of these (glibc, gcc, gdb, binutils), first in the course of
GNU/Hurd toolchain work, and later for CodeSourcery work, too.  Now, I
lost a bunch of my archives due to own stupidity -- and didn't preserve
most of the messages anyway, as they've been downloadable by anonymous
FTP, but are no more, as I had to figure out.  (And now, I found the
thread starting at
<http://sourceware.org/ml/overseers/2007-q3/msg00112.html>, continued at
<http://sourceware.org/ml/overseers/2007-q4/msg00013.html> to confirm
this.)

I very much prefer having the archives locally (and indexed / searchable
as I like it), instead of trying to extract what I'm occasionally looking
for from the web interface.  And no, I'm not going to sell email
addresses to spammers, etc.

I just had a chat with Ian L. Taylor in #overseers, and it seems that the
appropriate way to get hold of the archives is shell access to the
sourceware.org machine.

An option suggested by Ian was crawling the web list archives by HTTP
downloads (for the ``Raw text'' links), and re-constructing the original
messages (s%@% at% mangling, etc.) -- but I don't know if that was a
serious suggestions; it seems like unreasonable overhead to me (we're
talking about ten thousands of messages).

Likewise, I could talk to ezmlm to send me back each message; likely even
higher overhead.

I could use GMANE to export mbox files of gcc-patches starting in 2002,
for example.  Still, this seems illogical to me to rely on a third party
for this.

As I don't really want to bother you guys with this request too much, is
it possible to simply get shell access to the machine myself?


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

             reply	other threads:[~2011-02-07 22:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 22:46 Thomas Schwinge [this message]
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
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=878vxra2gl.fsf@kepler.schwinge.homeip.net \
    --to=thomas@schwinge.name \
    --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).