summaryrefslogtreecommitdiff
path: root/Documentation/git-index-pack.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-08-30 14:52:20 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-08-31 11:45:33 -0700
commit5907cda1b2e0bd7dc5c26466f60b9cbb60288cc5 (patch)
tree37738a51fd16874f47f6b978ef37aa1a2db00751 /Documentation/git-index-pack.txt
parentget_merge_bases_many(): walk from many tips in parallel (diff)
downloadtgif-5907cda1b2e0bd7dc5c26466f60b9cbb60288cc5.tar.xz
merge-base: "--is-ancestor A B"
In many scripted Porcelain commands, we find this idiom: if test "$(git rev-parse --verify A)" = "$(git merge-base A B)" then ... A is an ancestor of B ... fi But you do not have to compute exact merge-base only to see if A is an ancestor of B. Give them a more direct way to use the underlying machinery. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-index-pack.txt')
0 files changed, 0 insertions, 0 deletions