[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0807171259010.2959@woody.linux-foundation.org>
Date: Thu, 17 Jul 2008 13:01:17 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andi Kleen <andi@...stfloor.org>
cc: Ray Lee <ray-lk@...rabbit.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
"Rafael J. Wysocki" <rjw@...k.pl>, torvalds@...uxfoundation.org,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: Please pull ACPI updates
On Thu, 17 Jul 2008, Andi Kleen wrote:
>
> The whole point of the exercise of cleaning up/rewriting the history is to make
> the tree as bisectable as possible.
No.
"git bisect" is perfetly able to handle merges. They are _fine_.
The problem with rebasing is that it *changes* something that was already
tested (and possibly merged into somebody elses tree) into SOMETHING ELSE.
And that means that a large portion of the previous testing is basically
thrown away.
In particular, if something worked for somebody before, it also removes
the "known good state" from a bisection standpoint, so rebasing actually
makes things _harder_ to bisect - because now you cannot sanely bisect
between two versions of the tree (when you mark the old tree "good", it
has no relevance to the new tree that had all the old history rewritten).
So no, rebasing does _not_ make bisection easier. It makes it easier to
understand, perhaps, but it actually makes many things much much harder,
and removes all trace of any testing coverage that the old commit had.
Linus
--
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