| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 1 Jun 2011 06:22:25 +0000 From: Pavel Machek <pavel@....cz> To: "H. Peter Anvin" <hpa@...or.com> Cc: Steven Rostedt <rostedt@...dmis.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Turning off the incremental diff robot On Mon 2011-05-30 13:49:01, H. Peter Anvin wrote: > 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. -git1 to -git2 diffs are probably not useful. 2.6.39.1 to 2.6.39.2 diffs are useful IMO - people using stable kernels do not use git. I'm using -rc1 to -rc2 diffs. Useful :-). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists