#782284 git bisect does not make it easy to find which commit introduces a bug

Package:
git
Source:
git
Description:
fast, scalable, distributed revision control system
Submitter:
Arthur Marsh
Date:
2015-04-09 23:15:06 UTC
Severity:
wishlist
#782284#5
Date:
2015-04-09 23:10:56 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I found a long running bug fixed in a recent kernel and wanted to find
which commit fixed it.

git bisect did not allow me to call the current version "good" and the
old version "bad".

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I had to mentally switch what were "good" and "bad" during a bisect process.

   * What was the outcome of this action?
   * What outcome did you expect instead?

I expected to be allowed to mark a newer version "good" and an old version
"bad" to identify which commit fixed a bug.

*** End of the template - remove these template lines ***