All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Herrmann" <andreas.herrmann3@amd.com>
To: "Hank Leininger" <hlein@progressive-comp.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	B.Steinbrink@gmx.de,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Request for Linux Kernel Mailing List archives
Date: Wed, 12 Sep 2007 12:27:54 +0200	[thread overview]
Message-ID: <20070912102754.GA25889@alberich.amd.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706201210330.18771@marklar.spinoli.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2211 bytes --]

On Wed, Jun 20, 2007 at 12:38:48PM -0400, Hank Leininger wrote:
> 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.

Thanks for that usefull info.

Attached is a script containing a quick hack to enable look up of
a message-id at MARC with mutt(ng).

Posted to LKML just in case some other mutt(ng) user subscribed here
finds it useful.


Regards,

Andreas

-- 
Operating | AMD Saxony Limited Liability Company & Co. KG,
  System  | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 Research | Register Court Dresden: HRA 4896, General Partner authorized
  Center  | to represent: AMD Saxony LLC (Wilmington, Delaware, US)
  (OSRC)  | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy

[-- Attachment #2: show-mail.sh --]
[-- Type: application/x-sh, Size: 1344 bytes --]

  reply	other threads:[~2007-09-12 10:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 15:37 Request for Linux Kernel Mailing List archives 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
2007-09-12 10:27       ` Andreas Herrmann [this message]
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=20070912102754.GA25889@alberich.amd.com \
    --to=andreas.herrmann3@amd.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=hlein@progressive-comp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.