# [PATCH] "log --cherry-pick" documentation regression fix 1 messages from 2011-04-01 to 2011-04-01. Participants: Junio C Hamano. Thread: https://gitlist.dev/t/26961 ## Junio C Hamano, 2011-04-01 18:04 Subject: [PATCH] "log --cherry-pick" documentation regression fix Message-ID: <7v39m1hmpt.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7v39m1hmpt.fsf%40alter.siamese.dyndns.org ``` Earlier f98fd43 (git-log.txt,rev-list-options.txt: put option blocks in proper order, 2011-03-08) moved the text around in the documentation for options in the rev-list family of commands such as "log". Consequently, the description of the --cherry-pick option appears way above the description of the --left-right option now. But the description of the --cherry-pick option still refers to the example for the --left-right option, like this: ... with --left-right, like the example ABOVE in the description of that option. Rephrase it to clarify that we are making a forward reference. Signed-off-by: Junio C Hamano --- * I just happened to notice this one; there may be similar screw-ups due to this bulk text movement but I didn't look. Documentation/rev-list-options.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt index ea5c6c4..73111bb 100644 --- a/Documentation/rev-list-options.txt +++ b/Documentation/rev-list-options.txt @@ -179,8 +179,8 @@ endif::git-rev-list[] + For example, if you have two branches, `A` and `B`, a usual way to list all commits on only one side of them is with -`--left-right`, like the example above in the description of -that option. It however shows the commits that were cherry-picked +`--left-right` (see the example below in the description of +the `--left-right` option). It however shows the commits that were cherry-picked from the other branch (for example, "3rd on b" may be cherry-picked from branch A). With this option, such pairs of commits are excluded from the output. ```