summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-branches-one_branches-one
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2016-02-10 16:19:25 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-02-10 13:53:21 -0800
commitaac4fac1689f7d1414523d2ac96f1c737ee53b71 (patch)
tree86822b59844689a0e63b8c8e46ec7006e014a746 /t/t5515/fetch.br-branches-one_branches-one
parentcheck_filename: tighten dwim-wildcard ambiguity (diff)
downloadtgif-aac4fac1689f7d1414523d2ac96f1c737ee53b71.tar.xz
get_sha1: don't die() on bogus search strings
The get_sha1() function generally returns an error code rather than dying, and we sometimes speculatively call it with something that may be a revision or a pathspec, in order to see which one it might be. If it sees a bogus ":/" search string, though, it complains, without giving the caller the opportunity to recover. We can demonstrate this in t6133 by looking for ":/*.t", which should mean "*.t at the root of the tree", but instead dies because of the invalid regex (the "*" has nothing to operate on). We can fix this by returning an error rather than calling die(). Unfortunately, the tradeoff is that the error message is slightly worse in cases where we _do_ know we have a rev. E.g., running "git log ':/*.t' --" before yielded: fatal: Invalid search pattern: *.t and now we get only: fatal: bad revision ':/*.t' There's not a simple way to fix this short of passing a "quiet" flag all the way through the get_sha1() stack. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-branches-one_branches-one')
0 files changed, 0 insertions, 0 deletions