Patchwork D8201: help: clarify behavior of server.concurrent-push-mode

login
register
mail settings
Submitter phabricator
Date March 2, 2020, 3:24 a.m.
Message ID <differential-rev-PHID-DREV-t2voeqis7c37lmdzi4r2-req@mercurial-scm.org>
Download mbox | patch
Permalink /patch/45415/
State Superseded
Headers show

Comments

phabricator - March 2, 2020, 3:24 a.m.
valentin.gatienbaron created this revision.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.

REVISION SUMMARY
  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.

REPOSITORY
  rHG Mercurial

BRANCH
  default

REVISION DETAIL
  https://phab.mercurial-scm.org/D8201

AFFECTED FILES
  mercurial/helptext/config.txt

CHANGE DETAILS




To: valentin.gatienbaron, #hg-reviewers
Cc: mercurial-devel

Patch

diff --git a/mercurial/helptext/config.txt b/mercurial/helptext/config.txt
--- a/mercurial/helptext/config.txt
+++ b/mercurial/helptext/config.txt
@@ -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