Patchwork [2,of,4] revset: fix example describing how ordering is determined

login
register
mail settings
Submitter Yuya Nishihara
Date Aug. 30, 2017, 3:43 p.m.
Message ID <3b7bebd5335340797ee0.1504107780@mimosa>
Download mbox | patch
Permalink /patch/23510/
State Accepted
Headers show

Comments

Yuya Nishihara - Aug. 30, 2017, 3:43 p.m.
# HG changeset patch
# User Yuya Nishihara <yuya@tcha.org>
# Date 1504104810 -32400
#      Wed Aug 30 23:53:30 2017 +0900
# Node ID 3b7bebd5335340797ee0b3aab5fc17ada6c91fb8
# Parent  76c19e653cb1165f52242a398ed1d551e9ca5941
revset: fix example describing how ordering is determined

It was 'X & !Y' before.

Patch

diff --git a/mercurial/revset.py b/mercurial/revset.py
--- a/mercurial/revset.py
+++ b/mercurial/revset.py
@@ -64,13 +64,13 @@  fullreposet = smartset.fullreposet
 #
 # '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
-# 'ancesotrs(Z)', Z's order does not matter since 'ancesotrs' 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 'ancesotrs(Z)', Z's order does not matter
+# since 'ancesotrs' 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