From: "H. Peter Anvin" <hpa@zytor.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Should we force include <linux/err.h> when compiling all .c files?
Date: Wed, 30 Jul 2014 07:30:49 -0700 [thread overview]
Message-ID: <53D90199.2020108@zytor.com> (raw)
In-Reply-To: <20140729142439.GA1437@jtriplet-mobl1>
On 07/29/2014 07:24 AM, Josh Triplett wrote:
>>
>> We have such a clear procedure. It involves pre-arranging with Linus
>> *before the merge window begins* to run the script in question
>> *immediately before releasing rc1*.
>
> That sounds sensible. Is that documented anywhere?
>
In the brains of a bunch of kernel developers. This isn't a common
enough of a thing.
However, this is an exceptional procedure, and as I mentioned it isn't
even necessary in this case.
-hpa
prev parent reply other threads:[~2014-07-30 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 12:39 [Ksummit-discuss] Should we force include <linux/err.h> when compiling all .c files? David Howells
2014-07-25 23:24 ` Josh Triplett
2014-07-28 18:52 ` H. Peter Anvin
2014-07-28 20:16 ` Julia Lawall
2014-07-28 22:53 ` H. Peter Anvin
2014-07-29 14:35 ` Josh Triplett
2014-07-29 15:17 ` Luck, Tony
2014-07-29 16:50 ` Hugh Dickins
2014-07-29 19:06 ` Hugh Dickins
2014-07-29 14:24 ` Josh Triplett
2014-07-30 14:30 ` H. Peter Anvin [this message]
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=53D90199.2020108@zytor.com \
--to=hpa@zytor.com \
--cc=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.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 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.