Re: Porting digested new list archives to mail-archive

--===============3254361779925282492==
Content-Type: multipart/alternative; boundary=20cf307ac79f1c9ea60513ed4ae0

--20cf307ac79f1c9ea60513ed4ae0
Content-Type: text/plain; charset=ISO-8859-1

1. Yes, we override list name on import.
2. Search will have no concept of alternative list names. There is no
reasonable way to overcome this.
3. Why not use the tool that Earl mentioned?
4. We always merge into the new list name and set up an HTTP redirect so
that the old URLs are not broken. Merges are done via a manual request to
support staff.

--20cf307ac79f1c9ea60513ed4ae0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><br></div><div>1. Yes, we override list name on import.</div><div>2. S=
earch will have no concept of alternative list names. There is no reasonabl=
e way to overcome this.</div><div>3. Why not use the tool that Earl mention=
ed?</div><div>4. We always merge into the new list name and set up an HTTP =
redirect so that the old URLs are not broken. Merges are done via a manual =
request to support staff.</div>

--20cf307ac79f1c9ea60513ed4ae0--


--===============3254361779925282492==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gossip mailing list
https://www.mail-archive.com/gossip-piJqB+B6DfPJghKJT/[email protected]
https://www.mail-archive.com/cgi-bin/mailman/options/gossip
--===============3254361779925282492==--