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: Tue, 17 Apr 2007 08:49:37 +0200 From: Ingo Molnar <mingo@...e.hu> To: Peter Williams <pwil3058@...pond.net.au> Cc: linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Con Kolivas <kernel@...ivas.org>, Nick Piggin <npiggin@...e.de>, Mike Galbraith <efault@....de>, Arjan van de Ven <arjan@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, caglar@...dus.org.tr, Willy Tarreau <w@....eu>, Gene Heskett <gene.heskett@...il.com>, Dmitry Adamushko <dmitry.adamushko@...il.com> Subject: Re: [patch] CFS (Completely Fair Scheduler), v2 * Peter Williams <pwil3058@...pond.net.au> wrote: > Can I make a suggestion? > > Would it be possible (from now on) to publish changes relevant to the > previous patch (eventually leading to a series of patches that > describes the evolution of the new scheduler) so that it's easier for > us reviewers/critics to see the latest changes. E.g. if import such > changes into something like quilt (using my gquilt GUI wrapper, of > course :-)) I can then use meld (or similar) to follow what's going as > suggestions get folded in and bugs get fixed etc. the v1 patch is still downloadable so you can do a delta by first applying the v1 patch to a quilt queue, doing a 'quilt snapshot', then 'quilt pop', add the v2 patch to the series file, do a 'quilt push', then doing a "quilt diff --snapshot". (I just posted the delta patch in this thread so you can pick it from there too.) Ingo - 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