What does the last line of git bisect output mean?
I just ran bisect Git and got the following output:
547b115c69ab2ac7fde285c9b5653cbd8309a930 is the first bad commit
commit 547b115c69ab2ac7fde285c9b5653cbd8309a930
Author: Václav Slavík <vaclav@slavik.io>
Date: Sat Mar 14 13:35:32 2015 +0100
Use a floating tool window for Find
Keep the window on top of the parent frame at all times, don't show it
in taskbar and use the small "inspector" window decorations on OS X. The
latter is what couldn't be accomplished with wxDialog, so change to
using wxFrame and make the necessary changes.
:040000 040000 b1ed63b681bd41f924cbcf8214d65b65d7c2ea48 958a44d35851dae34b62d198a6b7f5685f490c89 M src
I understand everything except:
040000 040000 b1ed63b681bd41f924cbcf8214d65b65d7c2ea48 958a44d35851dae34b62d198a6b7f5685f490c89 M src
What does " 040000
" mean ? What hash are they?
source to share
It's about the path parameter on the first failed commit that has the changes causing the error.
You can also reduce the number of probes if you know which part of the tree is involved in the problem you are tracking by specifying path parameters
You can see more in the section Fighting regression with git bisect ":
And after the next few steps,
git bisect
"will eventually find the first bad commit:
$ git bisect bad
2ddcca36c8bcfa251724fe342c8327451988be0d is the first bad commit
commit 2ddcca36c8bcfa251724fe342c8327451988be0d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat May 3 11:59:44 2008 -0700
Linux 2.6.26-rc1
:100644 100644 5cf82581... 4492984e... M Makefile
Hashes are the SHA1 associated with a blob or tree that was passed as a parameter (SHA1 for good commit versus SHA for first bad commit) to facilitate diff.
In your case, "040000" is the file mode, one of which is:
-
100644
for a file (blob), -
100755
for an executable file (blob), -
040000
for a subdirectory (tree), -
160000
for a submodule (commit) or -
120000
for a blob that specifies the path of a symbolic link
source to share