From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kernel.org users] Turning off the incremental diff robot
Date: Tue, 31 May 2011 13:13:51 -0700 [thread overview]
Message-ID: <4DE54BFF.5090508@zytor.com> (raw)
In-Reply-To: <201105312204.02722.arnd@arndb.de>
On 05/31/2011 01:04 PM, Arnd Bergmann wrote:
>
> Are you talking about just ftp://ftp.kernel.org/pub/linux/kernel/*/incr/
> or also about ftp://ftp.kernel.org/pub/linux/kernel/v2.6/patch-* and
> Changelog-*?
>
> I can see reasons to keep the latter, but not necessarily the former.
>
The former only.
>>
>> Usecase one is zaurus, which is just not powerful enough for git, and
>> usecase two are companies that only work with releases... ketchup is
>> very useful for both.
>
> For usecase one, is it possible to replace the download links with
> links into http://git.kernel.org/ ?
>
> For usecase two, why wouldn't those be able to just download the entire
> release tarball? At least, I would expect that there is no need for
> the small incremental patches in their case, only for the full
> inter-release patches.
>
Zaurus I don't consider too important; anyone with a Zaurus is
realistically going to have a real development platform on hand.
-hpa
next prev parent reply other threads:[~2011-05-31 20:14 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
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 [this message]
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=4DE54BFF.5090508@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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