[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D9DD62E.2050308@zytor.com>
Date: Thu, 07 Apr 2011 08:20:14 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
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 04/07/2011 08:03 AM, Peter Zijlstra wrote:
>
> 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.
>
OK, this doesn't really need any hooks at all (the tip-bot is not a
hook). The committer is, and *has to be* responsible for getting the
unique string into the Link: tag, through whatever means they feel is
appropriate.
Based on the previous message, I'm going to modify the bot to recognize
the pattern:
Link: http://lkml.kernel.org/r/tip-`ranpwd -l 24`@....kernel.org
... to override the Message-ID. It seems like the least ugly of a lot
of ugly options.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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