summaryrefslogtreecommitdiff
path: root/test-subprocess.c
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-06-25 11:25:38 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-06-25 11:25:38 -0700
commita913b56fcbc86259f5422043e2f603e8738b158b (patch)
tree108c99e6ddd58333efd9447596cce82dd02e8c7e /test-subprocess.c
parentMerge branch 'lm/git-blame-el' (diff)
parentgit-cherry-pick.txt: clarify the use of revision range notation (diff)
downloadtgif-a913b56fcbc86259f5422043e2f603e8738b158b.tar.xz
Merge branch 'cn/cherry-pick-range-docs'
The command line argument of "git cherry-pick maint master..next" is just an ordinary revision range, which is unintuitive and at least deserves documentation. * cn/cherry-pick-range-docs: git-cherry-pick.txt: clarify the use of revision range notation Documentation: --no-walk is no-op if range is specified
Diffstat (limited to 'test-subprocess.c')
0 files changed, 0 insertions, 0 deletions