summaryrefslogtreecommitdiff
path: root/contrib/git-shell-commands/README
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2018-09-20 14:51:43 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-09-20 14:51:43 -0700
commit150f307afc13961b0322ad0e7205a7b193368586 (patch)
tree726a7011eab1d8fcf25654304901e6bb494e89c5 /contrib/git-shell-commands/README
parentMerge branch 'bp/checkout-new-branch-optim' (diff)
parentfetch doc: correct grammar in --force docs (diff)
downloadtgif-150f307afc13961b0322ad0e7205a7b193368586.tar.xz
Merge branch 'ab/fetch-tags-noclobber'
The rules used by "git push" and "git fetch" to determine if a ref can or cannot be updated were inconsistent; specifically, fetching to update existing tags were allowed even though tags are supposed to be unmoving anchoring points. "git fetch" was taught to forbid updates to existing tags without the "--force" option. This is a backward incompatible change but in a good way; it may still need to be treated carefully. * ab/fetch-tags-noclobber: fetch doc: correct grammar in --force docs push doc: add spacing between two words
Diffstat (limited to 'contrib/git-shell-commands/README')
0 files changed, 0 insertions, 0 deletions