From: Hank Leininger <hlein@progressive-comp.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: =?X-UNKNOWN?Q?Bj=F6rn_Steinbrink?= <B.Steinbrink@gmx.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Request for Linux Kernel Mailing List archives
Date: Wed, 20 Jun 2007 12:38:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706201210330.18771@marklar.spinoli.org> (raw)
In-Reply-To: <46794E5B.6070506@zytor.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; CHARSET=X-UNKNOWN; FORMAT=flowed, Size: 1848 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 20 Jun 2007, H. Peter Anvin wrote:
> Björn Steinbrink wrote:
>>
>> marc.info supports that.
>>
>> http://marc.info/?i=467949CC.9090405@zytor.com
>
> Excellent! Didn't see that documented anywhere.
=)
You're right, it's not really. In fact very little is documented.
You'd have to discover it -- in the message view, the Message-ID is
actually a self-referential link using the above syntax.
A few relevant points:
- - Such links never actually show you the corresponding message. Instead:
- If the message-id is unique, you are sent a 302 redirect to the
message using the normal MARC message URL (l=foo&msgid=123)
- If the message-id is not unique (such as crossposting, or deliberate
attempts to cause collisions) you'll be presented with a list of
messages, showing date, subject, author, and listname, to choose from.
- - MARC doesn't currently touch message bodies for spam-obfuscation
purposes, but it does for headers, specifically From: and Message-ID:.
When MARC generates message-id-based links, they are obfuscated.
But it can read in links formed either way. So, if you copy/paste the
target of a Message-ID: link out of MARC, it will look slightly
different than if you just made your own http://marc.info/?i=what@not,
but either form will work.
- - We don't use < > surrounding the message-id, but again, will accept
URLs formed either way.
- - We don't have Message-ID's for messages added before Dec, 2003.
Please feel free to ping me (offlist) with questions/concerns, hopefully
I will manage to respond :-P
Thanks,
Hank
-----BEGIN PGP SIGNATURE-----
iD8DBQFGeVgYqP26fHCT+PMRAsFHAJ9G2v+vrQ4g7VUAWEr1+Tb3dHDi3wCfRfho
sCYaEfLf9cJjGZtgpsCAPII=
=PpNt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-06-20 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 15:37 H. Peter Anvin
2007-06-20 15:52 ` Björn Steinbrink
2007-06-20 15:57 ` H. Peter Anvin
2007-06-20 16:38 ` Hank Leininger [this message]
2007-09-12 10:27 ` Andreas Herrmann
2007-06-20 18:10 ` Ben Pfaff
2007-06-21 6:21 ` Oleg Verych
2007-06-21 14:36 ` Oleg Verych
2007-06-21 15:06 ` David Woodhouse
2007-06-21 15:54 ` Björn Steinbrink
2007-06-21 15:56 ` David Woodhouse
2007-06-21 16:00 ` H. Peter Anvin
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.0706201210330.18771@marklar.spinoli.org \
--to=hlein@progressive-comp.com \
--cc=B.Steinbrink@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®