Documentation: --cherry-pick
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Apr 10, 2007 at 15:28 UTC
55a643ed1b9b9af4d3bd9dc934dfccd142d1c632
1 file changed
+15
Documentation/git-rev-list.txt
+15
@@ -22,6 +22,7 @@ SYNOPSIS
22
[ \--topo-order ]
23
[ \--parents ]
24
[ \--left-right ]
25
+ [ \--cherry-pick ]
26
[ \--encoding[=<encoding>] ]
27
[ \--(author|committer|grep)=<pattern> ]
28
[ [\--objects | \--objects-edge] [ \--unpacked ] ]
@@ -224,6 +225,20 @@ limiting may be applied.
225
In addition to the '<commit>' listed on the command
226
line, read them from the standard input.
227
228
+--cherry-pick::
229
+
230
+ Omit any commit that introduces the same change as
231
+ another commit on the "other side" when the set of
232
+ commits are limited with symmetric difference.
233
++
234
+For example, if you have two branches, `A` and `B`, a usual way
235
+to list all commits on only one side of them is with
236
+`--left-right`, like the example above in the description of
237
+that option. It however shows the commits that were cherry-picked
238
+from the other branch (for example, "3rd on b" may be cherry-picked
239
+from branch A). With this option, such pairs of commits are
240
+excluded from the output.
241
+
242
-g, --walk-reflogs::
243
244
Instead of walking the commit ancestry chain, walk