Mercurial Mercurial > mercurial / 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.
help: clarify behavior of server.concurrent-push-mode
authorValentin Gatien-Baron <valentin.gatienbaron@gmail.com>
Sun, 01 Mar 2020 21:16:45 -0500
changeset 44410 c85d5fd1a5d9
parent 44409 f935b680860d
child 44411 1e508097f570
help: clarify behavior of server.concurrent-push-mode So it doesn't seemingly say that old clients cannot talk to server configured with concurrent-push-mode=check-related. They can, they just don't get the benefit. Differential Revision: https://phab.mercurial-scm.org/D8201
mercurial/helptext/config.txt file | annotate | diff | comparison | revisions 
--- a/mercurial/helptext/config.txt	Fri Feb 28 10:30:18 2020 -0800
+++ b/mercurial/helptext/config.txt	Sun Mar 01 21:16:45 2020 -0500
@@ -2010,8 +2010,8 @@
     - 'check-related': push is only aborted if it affects head that got also
       affected while the push was preparing.
 
-    This requires compatible client (version 4.3 and later). Old client will
-    use 'strict'.
+    'check-related' only takes effect for compatible clients (version
+    4.3 and later). Older clients will use 'strict'.
 
 ``validate``
     Whether to validate the completeness of pushed changesets by
mercurial