summaryrefslogtreecommitdiff
path: root/Documentation/build-docdep.perl
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2015-08-29 01:04:18 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-08-31 09:34:20 -0700
commitce113604672fed9b429b1c162b1005794fff6a17 (patch)
tree21c002a890487c36226e5723666a2c5b363333ca /Documentation/build-docdep.perl
parentSixth batch for 2.5 cycle (diff)
downloadtgif-ce113604672fed9b429b1c162b1005794fff6a17.tar.xz
log: diagnose empty HEAD more clearly
If you init or clone an empty repository, the initial message from running "git log" is not very friendly: $ git init Initialized empty Git repository in /home/peff/foo/.git/ $ git log fatal: bad default revision 'HEAD' Let's detect this situation and write a more friendly message: $ git log fatal: your current branch 'master' does not have any commits yet We also detect the case that 'HEAD' points to a broken ref; this should be even less common, but is easy to see. Note that we do not diagnose all possible cases. We rely on resolve_ref, which means we do not get information about complex cases. E.g., "--default master" would use dwim_ref to find "refs/heads/master", but we notice only that "master" does not exist. Similarly, a complex sha1 expression like "--default HEAD^2" will not resolve as a ref. But that's OK. We fall back to a generic error message in those cases, and they are unlikely to be used anyway. Catching an empty or broken "HEAD" improves the common case, and the other cases are not regressed. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/build-docdep.perl')
0 files changed, 0 insertions, 0 deletions