projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: 6a7f2b2 b98878e)
Merge branch 'cn/cherry-pick-range-docs'
authorJunio C Hamano <gitster@pobox.com>
Mon, 25 Jun 2012 18:25:38 +0000 (11:25 -0700)
committerJunio C Hamano <gitster@pobox.com>
Mon, 25 Jun 2012 18:25:38 +0000 (11:25 -0700)
commita913b56fcbc86259f5422043e2f603e8738b158b
tree108c99e6ddd58333efd9447596cce82dd02e8c7etree | snapshot
parent6a7f2b239634d05f828adc09a90578f307aa94f2commit | diff
parentb98878edefd284927748aa2ce9ff090fa43c2c8acommit | diff
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
Documentation/git-cherry-pick.txt diff1 | diff2 | blob | history
Documentation/rev-list-options.txt diff1 | diff2 | blob | history
Git—the stupid content tracker