summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2008-02-24 01:14:17 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-02-27 21:26:30 (GMT)
commit0f497e75f05cdf0c0c1278eaba898cda6f118d71 (patch)
tree0ecf5e9861cd7164a86a418cfd7fb804fc059ed3 /Documentation
parent7a0a34ca6f31c6bb5d24ccc0cdab606736d7a322 (diff)
downloadgit-0f497e75f05cdf0c0c1278eaba898cda6f118d71.zip
git-0f497e75f05cdf0c0c1278eaba898cda6f118d71.tar.gz
git-0f497e75f05cdf0c0c1278eaba898cda6f118d71.tar.bz2
Eliminate confusing "won't bisect on seeked tree" failure
This error message is very confusing---it doesn't tell the user anything about how to fix the situation. And the actual fix for the situation ("git bisect reset") does a checkout of a potentially random branch, (compared to what the user wants to be on for the bisect she is starting). The simplest way to eliminate the confusion is to just make "git bisect start" do the cleanup itself. There's no significant loss of safety here since we already have a general safety in the form of the reflog. Note: We preserve the warning for any cogito users. We do this by switching from .git/head-name to .git/BISECT_START for the extra state, (which is a more descriptive name anyway). Signed-off-by: Carl Worth <cworth@cworth.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions