From: Giel van Schijndel <me@mortis.eu>
To: Lin Ming <lin@ming.vg>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Why not make LKML-Reference useful?
Date: Tue, 14 Sep 2010 12:17:51 +0200 [thread overview]
Message-ID: <20100914101751.GH29094@salidar.me.mortis.eu> (raw)
In-Reply-To: <AANLkTin9Ry6hCBciLkg2ExgERv9SHq5vO-Zvxy3Ei_JJ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Tue, Sep 14, 2010 at 05:52:26PM +0800, Lin Ming wrote:
> What's LKML-Reference in the kernel git log?
> In my understanding, it's a link to the original discussion of the
> patch on LKML, for example
>
> LKML-Reference: http://marc.info/?l=linux-kernel&m=128445596126705&w=2
>
> But I never see such a link in the LKML-Reference of the git log.
>
> Those LKML-Reference are really useless.
No they're not, those are the Message-IDs of the referenced headers
which can be used to search archives with.
> Why not put a link in LKML-Reference?
Now, links OTOH *would* be useless on the long run as there's no single
entity maintaining LKML archives, so whatever entity you link to, you
become dependent on. Having Message-IDs at least allows you to search
any available archive (provided it allows searching on Message-IDs).
--
Met vriendelijke groet,
With kind regards,
Giel van Schijndel
--
"Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live."
-- Rick Osborne
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-09-14 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 9:52 Lin Ming
2010-09-14 10:17 ` Giel van Schijndel [this message]
2010-09-14 10:25 ` Daniel K.
2010-09-14 10:47 ` Johannes Stezenbach
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=20100914101751.GH29094@salidar.me.mortis.eu \
--to=me@mortis.eu \
--cc=lin@ming.vg \
--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®