The KWin Coding Style Situation

[Matthias Fuchs]

Am Sonntag 28 November 2010, 22:48:56 schrieb Aaron J. Seigo:
> so yes, a reformat will create an "opaque membrane" in the history of the
> repository, but wether that is actually a problem or not comes down to the
> development practices around kwin. e.g. how important is it to git bisect N
> months in the past?

git bisect should work as normal as that are mostly white space changes.

Further it is possible to skip commits with
git bisect skip $VERSION
also a tag could be used there if one exists.

So suppose the change was done in multiple commits after the tag 
"codeStyleChangeBefore" and ending with "codeStyleChangeAfter" -- no other 
commits inbetween,
then you'd do
git bisect skip codeStyleChangeBefore..codeStyleChangeAfter to skip all 
commits that change the code style.