summaryrefslogtreecommitdiff
path: root/builtin/describe.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-03-30 21:07:16 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-03-30 21:07:16 (GMT)
commit42e1cc517b2a57fa2fad6cc41238bfdbc3f4b9d7 (patch)
tree30bfc05a903be4375b5330d374ffdefc48686a9a /builtin/describe.c
parente7cbfd98e3a960450025b58f6678e17c9c01b007 (diff)
parent244ea1b5e49081530e0ba5c717db1fdbe2bda73e (diff)
downloadgit-42e1cc517b2a57fa2fad6cc41238bfdbc3f4b9d7.zip
git-42e1cc517b2a57fa2fad6cc41238bfdbc3f4b9d7.tar.gz
git-42e1cc517b2a57fa2fad6cc41238bfdbc3f4b9d7.tar.bz2
Merge branch 'ab/case-insensitive-upstream-and-push-marker'
On many keyboards, typing "@{" involves holding down SHIFT key and one can easily end up with "@{Up..." when typing "@{upstream}". As the upstream/push keywords do not appear anywhere else in the syntax, we can safely accept them case insensitively without introducing ambiguity or confusion to solve this. * ab/case-insensitive-upstream-and-push-marker: rev-parse: match @{upstream}, @{u} and @{push} case-insensitively
Diffstat (limited to 'builtin/describe.c')
0 files changed, 0 insertions, 0 deletions