Does "git bisect log" keep all state information? -
motivation
i doing bisection , considering saving state, maybe continue later. it's not clear if git bisect log
can that.
search before post
man git bisect
says:
bisect log , bisect replay
after having marked revisions or bad, issue following command show has been done far:
$ git bisect log
if discover made mistake in specifying status of revision, can save output of command file, edit remove incorrect entries, , issue following commands return corrected state:
$ git bisect reset $ git bisect replay that-file
compare fighting regressions git bisect seems more suggest answer yes.
saving log , replaying it
if want show other people bisection process, can log using example:
$ git bisect log > bisect_log.txt
and possible replay using:
$ git bisect replay bisect_log.txt
experiment
i did experiment check git 1.9.0.
tar zcvf git.tgz .git git bisect log >bisectlog git reset --hard git bisect replay bisectlog not bisecting. bisecting: 2 revisions left test after (roughly 2 steps) [somehash] commit log tar zdf git.tgz .git/bisect_ancestors_ok: mod time differs .git/bisect_expected_rev: mod time differs .git/bisect_log: mod time differs .git/bisect_log: size differs .git/bisect_names: mod time differs .git/bisect_start: mod time differs .git/head: mod time differs .git/index: mod time differs .git/index: contents differ .git/logs/head: mod time differs .git/logs/head: size differs .git/orig_head: mod time differs .git/orig_head: contents differ .git/refs/bisect/bad: mod time differs .git/refs/bisect/good-0702dc7ec1d80d8ed38d7fe597dc0cce98ddccfc: mod time differs .git/refs/bisect/good-07357488ecac01085e6a5df1e4d44e00da4842e5: mod time differs .git/refs/bisect/good-5b753b5d63f16b60f5ccd6a954cf2f92e721af08: mod time differs .git/refs/bisect/good-5fac8a8900d5a27bbdf4bebd8b49cfef9757a4e3: mod time differs .git/refs/bisect/good-b2a73d5c02353589a81fb247255f78c41137299a: mod time differs .git/refs/bisect/good-f3f89511415bf386a6d4c815b92c9d3679a5e2eb: mod time differs
git bisect log | diff - bisectlog
25a26 > # first bad commit: [someotherhash] other commit message
conclusion
so, after replaying this, git bisect log
lost 1 line.
i'd git bisect log
contains of information, not all.
note: bisection used experiment implied several manual reset other commits, might explain something.
has asked oneself same question?
should 1 care missing line?
Comments
Post a Comment