From: "H. Peter Anvin" <hpa@zytor.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Turning off the incremental diff robot
Date: Mon, 30 May 2011 13:49:01 -0700 [thread overview]
Message-ID: <4DE402BD.4060407@zytor.com> (raw)
In-Reply-To: <20110530194500.GE10792@home.goodmis.org>
On 05/30/2011 12:45 PM, Steven Rostedt wrote:
> On Mon, May 30, 2011 at 12:03:03PM -0700, H. Peter Anvin wrote:
>> Hi all,
>>
>> With the v3.0 name change I was looking over what might break, and I'm
>> seriously considering turning off the incremental diff robot on
>> kernel.org. It's not clear to me that it is actually useful anymore,
>> with git and all.
>
> What is the incremental diff robot?
>
> Does it make the patches between 2.6.x to 2.6.x+1?
>
No, but it generates the patches between, say, 2.6.x.y and 2.6.x.y+1 or
2.6.x-rcy and 2.6.x-rcy+1. Anything in an "incr" directory.
-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-05-30 20:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 19:03 Turning off the incremental diff robot H. Peter Anvin
2011-05-30 19:45 ` Steven Rostedt
2011-05-30 20:10 ` Randy Dunlap
2011-05-30 20:49 ` H. Peter Anvin [this message]
2011-05-31 12:38 ` Heiko Carstens
2011-05-31 12:49 ` Steven Rostedt
2011-06-01 6:22 ` Pavel Machek
2011-05-31 19:43 ` [kernel.org users] " Pavel Machek
2011-05-31 20:04 ` Arnd Bergmann
2011-05-31 20:13 ` H. Peter Anvin
2011-05-31 20:31 ` Pavel Machek
2011-05-31 19:52 ` Willy Tarreau
2011-05-31 20:13 ` H. Peter Anvin
2011-06-01 8:43 ` Tvrtko Ursulin
2011-06-01 15:46 ` H. Peter Anvin
2011-06-01 13:09 ` Jean Delvare
2011-06-01 13:34 ` Alexey Dobriyan
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=4DE402BD.4060407@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox