##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

configitems: enable pullbundles by default...
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").
Mathias De Mare - - Load All Authors

File last commit:

r50472:53e4f44b default
r50472:53e4f44b default
Show More
next
28 lines | 855 B | text/plain | TextLexer
/ relnotes / next
History | Annotation | Raw |Copy content |Copy permalink
= Mercurial XXX =
== New Features ==
== Default Format Change ==
These changes affect newly created repositories (or new clones) done with
Mercurial XXX.
== New Experimental Features ==
== Bug Fixes ==
== Backwards Compatibility Changes ==
* chg worker processes will now correctly load per-repository configuration
when given a both a relative `--repository` path and an alternate working
directory via `--cwd`. A side-effect of this change is that these workers
will now return an error if hg cannot find the current working directory,
even when a different directory is specified via `--cwd`.
== 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.