From: "H. Peter Anvin" <hpa@zytor.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: tip: New "Link:" tag to replace "LKML-Reference:"
Date: Thu, 07 Apr 2011 07:56:12 -0700 [thread overview]
Message-ID: <4D9DD08C.2080101@zytor.com> (raw)
In-Reply-To: <1302188050.9086.27.camel@twins>
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.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2011-04-07 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 22:09 tip: New "Link:" tag to replace "LKML-Reference:" H. Peter Anvin
2011-04-07 14:08 ` Peter Zijlstra
2011-04-07 14:43 ` H. Peter Anvin
2011-04-07 14:54 ` Peter Zijlstra
2011-04-07 14:56 ` H. Peter Anvin [this message]
2011-04-07 15:03 ` Peter Zijlstra
2011-04-07 15:20 ` H. Peter Anvin
2011-04-07 15:26 ` Peter Zijlstra
2011-04-08 19:05 ` Link: tags for new submission -- UPDATE H. Peter Anvin
2011-04-07 15:03 ` tip: New "Link:" tag to replace "LKML-Reference:" H. Peter Anvin
2011-04-07 15:28 ` Sam Ravnborg
2011-04-07 15:58 ` H. Peter Anvin
2011-04-08 14:36 ` Bjorn Helgaas
2011-04-08 18:45 ` 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=4D9DD08C.2080101@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.