[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1302188635.9086.44.camel@twins>
Date: Thu, 07 Apr 2011 17:03:55 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: tip: New "Link:" tag to replace "LKML-Reference:"
On Thu, 2011-04-07 at 07:56 -0700, H. Peter Anvin wrote:
> On 04/07/2011 07:54 AM, Peter Zijlstra wrote:
> >
> > Can't we use a prepare-commit-msg or commit-msg hook to re-write the
> > commit message to include a Link tag when one is missing, using
> > something like:
> >
> > Link: http://lkml.kernel.org/r/tip-$SHA@git.kernel.org
> >
> > And have the post-commit hook that sends the messages recognize this
> > form and send the message using the correct msgid.
> >
> > That way the commit includes a correct and clickable link, doesn't
> > require magic knowledge and doesn't need the committer to do extra work.
> >
>
> Think about it... hint: the SHA1 is a cryptographically secure signature
> of the commit object.
D'0h ok.. but the scheme would work with any generated msgid, all we
need is to generate one for commits that lack a Link tag and insert it
using the prepare-commit-msg/commit-msg hooks and for the post-commit
hook to recognize it and use that actual msgid.
The only thing to avoid is msgid collision, but given that MUAs already
have this problem all we need to do is borrow some of their logic.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists