From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
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 17:26:05 +0200 [thread overview]
Message-ID: <1302189965.9086.71.camel@twins> (raw)
In-Reply-To: <4D9DD62E.2050308@zytor.com>
On Thu, 2011-04-07 at 08:20 -0700, H. Peter Anvin wrote:
>
> 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`@git.kernel.org
>
> ... to override the Message-ID. It seems like the least ugly of a lot
> of ugly options.
OK, but to qualify, it needn't be the committer, that is, Ingo usually
commits the stuff for me, but I usually provide him with complete
patches including LKML-Reference, now Link, tag.
I'll change my script to:
Use an existing Link tag provided it doesn't match the above pattern, if
there's no such tag, use Message-id, lacking that, generate one using
the above pattern.
Thanks!
next prev parent reply other threads:[~2011-04-07 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 22:09 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
2011-04-07 15:03 ` Peter Zijlstra
2011-04-07 15:20 ` H. Peter Anvin
2011-04-07 15:26 ` Peter Zijlstra [this message]
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=1302189965.9086.71.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome