Mercurial Mercurial > hg-stable / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
revset: fix example describing how ordering is determined
authorYuya Nishihara <yuya@tcha.org>
Wed, 30 Aug 2017 23:53:30 +0900
changeset 34035 62cc1f17c571
parent 34034 96f249dce03e
child 34036 de286200f722
revset: fix example describing how ordering is determined It was 'X & !Y' before.
mercurial/revset.py file | annotate | diff | comparison | revisions 
--- a/mercurial/revset.py	Wed Aug 30 22:32:47 2017 +0900
+++ b/mercurial/revset.py	Wed Aug 30 23:53:30 2017 +0900
@@ -64,13 +64,13 @@
 #
 # 'any' means the order doesn't matter. For instance,
 #
-#   (X & Y) | ancestors(Z)
-#        ^              ^
-#        any            any
+#   (X & !Y) | ancestors(Z)
+#         ^              ^
+#         any            any
 #
-# For 'X & Y', 'X' decides order so the order of 'Y' does not matter. For
-# 'ancestors(Z)', Z's order does not matter since 'ancestors' does not care
-# about the order of its argument.
+# For 'X & !Y', 'X' decides the order and 'Y' is subtracted from 'X', so the
+# order of 'Y' does not matter. For 'ancestors(Z)', Z's order does not matter
+# since 'ancestors' does not care about the order of its argument.
 #
 # Currently, most revsets do not care about the order, so 'define' is
 # equivalent to 'follow' for them, and the resulting order is based on the
hg-stable