Re: [Tools-discuss] historic mailing list archives
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tools-discuss] historic mailing list archives
Lars Eggert wrote:
> I don't think the IETF can depend on gmane or any
> other external archiving service.
Apparently it does in the case of the newtrk archive,
or various "other lists". Depending on how Google
indexes such archives is also risky. I just found
that Google changed the format of "CSE annotation"
files *again*, i.e. shortly after the documentation
was in a remotely understandable state what really
happens is *again* unrelated to this documentation.
I didn't have "*.psg.com/*" and added that, before
that addition I got 69 hits for "clean slate rrg":
<http://purl.net/xyzzy/-a9/clean+slate+rrg>
Now I get less hits (62), LOL. But with the dupes
included PSG.COM shows up, 100 hits. The effect
depends also on the order of the keywords, 56 hits
for <http://purl.net/xyzzy/-a9/rrg+clean+slate>
> too many past examples of such services that have
> been used to host IETF lists that have disappeared,
> as evidenced by the defunct archive links on
> http://tools.ietf.org/wg/concluded
That list only has the former "original" archives,
for Newtrk you could use a still existing archive
in your CSE.
My GMaNe search pattern proposal was too complex:
>> <http://permalink.gmane.org/gmane.ietf.newtrk/*>
>> <http://article.gmane.org/gmane.ietf.newtrk/*>
<http://*.gmane.org/gmane.ietf.newtrk/*> is enough.
>> <http://permalink.gmane.org/gmane.ietf.*>
>> <http://article.gmane.org/gmane.ietf.*>
Ditto, check out <http://*.gmane.org/gmane.ietf.*>.
Maybe you can reconstruct some lost IETF archives
such as Newtrk using the GMaNe export feature, but
it would be a huge project when you take various
sources down to raw ftp.ietf.org mbox archives...
Frank
_______________________________________________
Tools-discuss mailing list
Tools-discuss at ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.