changeset 49577:53e4f44ba0e8

configitems: enable pullbundles by default The use of pullbundles is already protected: they are only used when a pullbundles.manifest file is created on the server. Having an additional flag doesn't really make sense and can confuse users (as indicated in the mercurial mailing list on the topic "Can't get pull-bundles working").
author Mathias De Mare <mathias.de_mare@nokia.com>
date Mon, 07 Nov 2022 09:25:20 +0100
parents bbbb5213d043
children 18282cf18aa2
files mercurial/configitems.py relnotes/next tests/test-pull-bundle.t
diffstat 3 files changed, 5 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/mercurial/configitems.py	Fri Nov 04 22:59:16 2022 -0400
+++ b/mercurial/configitems.py	Mon Nov 07 09:25:20 2022 +0100
@@ -2123,7 +2123,7 @@
 coreconfigitem(
     b'server',
     b'pullbundle',
-    default=False,
+    default=True,
 )
 coreconfigitem(
     b'server',
--- a/relnotes/next	Fri Nov 04 22:59:16 2022 -0400
+++ b/relnotes/next	Mon Nov 07 09:25:20 2022 +0100
@@ -22,3 +22,7 @@
 == Internal API Changes ==
 
 == Miscellaneous ==
+
+ * pullbundle support no longer requires setting a server-side option,
+   providing a .hg/pullbundles.manifest according to the syntax specified in
+   'hg help -e clonebundles' is enough.
--- a/tests/test-pull-bundle.t	Fri Nov 04 22:59:16 2022 -0400
+++ b/tests/test-pull-bundle.t	Mon Nov 07 09:25:20 2022 +0100
@@ -33,8 +33,6 @@
 
   $ cd repo
   $ cat <<EOF > .hg/hgrc
-  > [server]
-  > pullbundle = True
   > [experimental]
   > evolution = True
   > [extensions]