summaryrefslogtreecommitdiff
path: root/builtin-pack-refs.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2009-10-27 18:28:07 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-10-28 23:07:43 (GMT)
commitad3f9a71a8200418e1da59b9712a8fde3f8c4c08 (patch)
tree479385bc6adfc7e47a26ff15c90cf24329f54d45 /builtin-pack-refs.c
parent78d553b7d7b269bb22ebd8b1198657c37484a3a0 (diff)
downloadgit-ad3f9a71a8200418e1da59b9712a8fde3f8c4c08.zip
git-ad3f9a71a8200418e1da59b9712a8fde3f8c4c08.tar.gz
git-ad3f9a71a8200418e1da59b9712a8fde3f8c4c08.tar.bz2
Add '--bisect' revision machinery argument
I personally use "git bisect visualize" all the time when I bisect, but it turns out that that is not a very flexible model. Sometimes I want to do bisection based on all commits (no pathname limiting), but then visualize the current bisection tree with just a few pathnames because I _suspect_ those pathnames are involved in the problem but am not totally sure about them. And at other times, I want to use other revision parsing logic, none of which is available with "git bisect visualize". So this adds "--bisect" as a revision parsing argument, and as a result it just works with all the normal logging tools. So now I can just do gitk --bisect --simplify-by-decoration filename-here etc. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin-pack-refs.c')
0 files changed, 0 insertions, 0 deletions