linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, linuxppc-dev-owner@lists.ozlabs.org
Subject: Re: mailing list moving
Date: Sat, 06 Jun 2009 18:37:47 +1000	[thread overview]
Message-ID: <1244277467.4277.12.camel@concordia> (raw)
In-Reply-To: <20090605190831.c5d59095.sfr@canb.auug.org.au>

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

On Fri, 2009-06-05 at 19:08 +1000, Stephen Rothwell wrote:
> Hi Michael,
> 
> On Fri, 05 Jun 2009 17:38:40 +1000 Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > On Fri, 2009-06-05 at 17:26 +1000, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > On Sun, 31 May 2009 15:09:50 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > 
> > > The archives on lists.ozlabs.org (and ozlabs.org) have unfortunately not
> > > retained their URLs (the basename of the article URLs changed). 
> > 
> > Would a rewrite rule fix it? It'd be nice for them to keep working.
> 
> No, because the actual article numbers changed when I rebuilt the archive
> on the new server.
> 
> Sorry.
> 
> I do, however, have the old archives, so maybe we can do something ...

We could use the old archive to work out the mapping between old and new
and write a billion rewrite rules, but it'd probably crash the rewrite
code - and if not slow the server to a crawl.

So into the too hard basket I think :)

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-06  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31  5:09 mailing list moving Stephen Rothwell
2009-06-05  7:26 ` Stephen Rothwell
2009-06-05  7:38   ` Michael Ellerman
2009-06-05  9:08     ` Stephen Rothwell
2009-06-06  8:37       ` Michael Ellerman [this message]
2009-06-08  8:56         ` Arnd Bergmann

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=1244277467.4277.12.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=linuxppc-dev-owner@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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 NNTP newsgroup(s).