From: Jean Delvare <khali@linux-fr.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kernel.org users] Turning off the incremental diff robot
Date: Wed, 1 Jun 2011 15:09:15 +0200 [thread overview]
Message-ID: <20110601150915.4af71a0a@endymion.delvare> (raw)
In-Reply-To: <4DE3E9E7.8020008@zytor.com>
Hi Peter,
On Mon, 30 May 2011 12:03:03 -0700, H. Peter Anvin wrote:
> 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.
>
> Do anyone actually use these anymore?
Do you mean files in testing/incr such as patch-2.6.39-rc6-rc7.bz2?
Yes, I am still using these. That being said:
* I guess I could extract these myself from git with a simple git
diff command?
* I don't give a damn to older incremental patches, only to the ones of
the current development cycle.
So if you want to delete all the old files, I'm all for it, and if you
decide to no longer generate the incremental patches at all, I can live
with it.
--
Jean Delvare
next prev parent reply other threads:[~2011-06-01 13:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 19:03 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
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 [this message]
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=20110601150915.4af71a0a@endymion.delvare \
--to=khali@linux-fr.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®