- User Since
- Jul 11 2017, 12:05 PM (74 w, 13 h)
Mon, Dec 10
Sun, Dec 9
Thu, Dec 6
Tue, Dec 4
Mon, Dec 3
Sun, Dec 2
Sat, Dec 1
The default only affects the creation of new repositories. Nothing will change for existing repository.
- If enabled by default in 4.9, will a user who uses some old mercurial like 4.6 or 4.0 will be able to clone a repository created by hg-4.9?
Sure, as for the previous changes (eg: general-delta), everything is fully compatible over the wire. Mercurial 1.9 could successfully pull and push from a 4.9 server using sparse-revlog.
- Will a client who is non-sparse revlog enabled be able to interact with a server who is sparse revlog enabled?
Absolutely, same as for the previous requirements introduction.
I am not following the work closely so these questions.
It now seems mature enough to be enabled by default.
While I don't know much about revlog internals, I do see a lot of patches related to sparse revlog being pushed in this cycle which is great. The concern is that those patches are not yet a part of release. In other words, I am not feeling confident that it's much tested yet.