# HG changeset patch
# User Yuya Nishihara <yuya@tcha.org>
# Date 1504104810 -32400
# Node ID 62cc1f17c571d7ff917421afed061a48ba00b6cc
# Parent  96f249dce03ef5d308c7ab8e406e0527b91aae0b
revset: fix example describing how ordering is determined

It was 'X & !Y' before.

diff -r 96f249dce03e -r 62cc1f17c571 mercurial/revset.py
--- 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