aboutsummaryrefslogtreecommitdiff
path: root/sha1_file.c
diff options
context:
space:
mode:
authorSZEDER Gábor <szeder@ira.uka.de>2008-11-28 01:46:38 +0100
committerJunio C Hamano <gitster@pobox.com>2008-11-27 18:34:30 -0800
commit608efb875f89a946d5cb37b2dd4077132618e0e1 (patch)
tree1ba1a512894bc7daeb7e6b9c447eb6b8a96bec47 /sha1_file.c
parent76bac89036abd73a4a32fd494a34dcc3340fef1a (diff)
downloadgit-608efb875f89a946d5cb37b2dd4077132618e0e1.tar.gz
git-608efb875f89a946d5cb37b2dd4077132618e0e1.tar.xz
bash: complete full refs
Sometimes it's handy to complete full refs, e.g. the user has some refs outside of refs/{heads,remotes,tags} or the user wants to complete some git command's special refs (like 'git show refs/bisect/bad'). To do that, we check whether the ref to be completed starts with 'refs/' or is 'refs' (to reduce the risk of matching 'refs-'). If it does, then we offer full refs for completion; otherwise everything works as usual. This way the impact on the common case is fairly small (hopefully not many users have branches or tags starting with 'refs'), and in the special case the cost of typing out 'refs' is bearable. While at it, also remove the unused 'cmd' variable from '__git_refs'. Signed-off-by: SZEDER Gábor <szeder@ira.uka.de> Acked-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'sha1_file.c')
0 files changed, 0 insertions, 0 deletions