summaryrefslogtreecommitdiff
path: root/t/t4109
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2017-03-30 14:07:16 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-03-30 14:07:16 -0700
commit42e1cc517b2a57fa2fad6cc41238bfdbc3f4b9d7 (patch)
tree30bfc05a903be4375b5330d374ffdefc48686a9a /t/t4109
parentMerge branch 'ab/doc-submitting' (diff)
parentrev-parse: match @{upstream}, @{u} and @{push} case-insensitively (diff)
downloadtgif-42e1cc517b2a57fa2fad6cc41238bfdbc3f4b9d7.tar.xz
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 't/t4109')
0 files changed, 0 insertions, 0 deletions