[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200807161552.53427.bzolnier@gmail.com>
Date: Wed, 16 Jul 2008 15:52:53 +0200
From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [git pull] x86 changes for v2.6.27
Hi,
On Monday 14 July 2008, Ingo Molnar wrote:
> Linus,
>
> Please pull the latest x86 git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86/for-linus
>
> this is our first merge window since we migrated over to a pure Git
> based patch management setup and integrated x86.git into the -tip tree.
> Going from Quilt to Git was quite hard for this
> 1000-patches-per-kernel-cycle tree, so please bear with us :-)
I see that fix patches are no longer folded into the guilty patch
and it makes me a bit worried about kernel bisectability (on which
many people depend on for hunting regressions)...
Random example (amongst many others) of what I mean:
[...]
> x86: introduce max_low_pfn_mapped for 64-bit
> x86: max_low_pfn_mapped fix, #1
> x86: max_low_pfn_mapped fix, #2
> x86: max_low_pfn_mapped fix, #3
There is also a _ton_ of build fixes which could have been easily
folded into guilty patches.
Could you please consider adding this additional step into your
development process before push to Linus?
Thanks,
Bart
--
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