[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080614090023.GA13798@elte.hu>
Date: Sat, 14 Jun 2008 11:00:23 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Vegard Nossum <vegard.nossum@...il.com>
Cc: Pekka Enberg <penberg@...helsinki.fi>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] kmemcheck: divide and conquer
* Vegard Nossum <vegard.nossum@...il.com> wrote:
> http://git.kernel.org/?p=linux/kernel/git/vegard/kmemcheck.git;a=commit;h=8c67b9b8005a518ce003943a64c37a9fc2c84485
>
> But for the newer versions, I've merged it into the "kmemcheck core"
> commit. To pick up the whole series, you can either check out the
> against-v2.6.26-rc5 branch (which is frozen), or you can check out the
> "current" branch which is the most recent rebase (against v2.6.26-rc6,
> but not yet frozen):
a small workflow request: could you please start adding append-only
commits to that tree, if possible? For example right now as it looks the
kmemcheck tree says:
commit 385e31b9eae0528bada07d16a189f3f40df23961
Author: Vegard Nossum <vegard.nossum@...il.com>
Date: Fri Apr 4 00:51:41 2008 +0200
kmemcheck: add the kmemcheck core
i had to look around for a few minutes to make sure i got the right
branch until i realized that "Apr 4" is not the correct date - this
commit got updated by you just today.
it would be much better if you stopped rebasing kmemcheck from now on,
and did append-only updates only - that way i could pick up your updates
into tip/kmemcheck by doing pulls. It does not matter if the result
looks a bit messier - most of the fundamentals should be in place
already.
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