Re: current git kernel has strange problems during bisect

From: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Date: Jan 11, 2009, 19:47 UTC
Message-ID: <f19298770901111147t625a2161t779bfcfc0317225c@mail.gmail.com>
In-Reply-To: <20090111194258.GA4840@uranus.ravnborg.org>

On Sun, Jan 11, 2009 at 22:42, Sam Ravnborg <sam@ravnborg.org> wrote:

Show 18 quoted lines

>>
>> For bisect, it's indeed somewhat annoying, and we could have perhaps done
>> some things a bit differently, but it's about the closest you can get to
>> "real history" without making the first btrfs merge-point a _total_
>> disaster.
>>
>> For bisect purposes, if you know you're not chasing down a btrfs issue,
>> you can do
>>
>>       git bisect good 34353029534a08e41cfb8be647d734b9ce9ebff8
>>
>> where that commit 34353029 is the last one which has _just_ the btrfs
>> files. The next commit is when it does "Merge Btrfs into fs/btrfs", and
>> that one has the whole kernel tree again.
>
> The cost of moving this piece of history from one git tree to another
> git tree is that we make it harder to debug the kernel for the advanced user
> that knows how to do bisect.

And wasn't is trivial to avoid? Just exporting the commits as patches and importing them into the kernel tree would preserve the history, and not break bisection.