Enabling evolution bitbucket side (or any other server)

[Pierre-Yves David]

Hi Brodie,
(cc the list as it may interest other people)

Early last week I update the `simple4server.py` extensions to make sure:

- it was properly tested,
- it was working with mercurial 2.9.1,
- it had a way to disable the feature on a repo basis.

It should now be ready for deployment at bitbucket as discussed during 
the mini-sprint.

Where is it?
============

This current state of the extension live in the head of default of the 
mutable history repo:

repo:      https://bitbucket.org/marmoute/mutable-history/
Branch:    default
file:      hgext/simple4server.py

You update to the current default head. (its currently
6cb81dbb95163806f31522a17f01cff25daf9708 for the record)

make sure you use simple4server.py. Evolve.py focus on client side 
capability and is not compatible with 2.9.1 in default.

Enabling obsolescence marker on a repo basis
============================================

simple4server will turn the evolution feature on. Making core mercurial 
happy to create and transmit obsolescence marker.

The current the obsolescence marker exchanges used in core mercurial is 
very slow and ineffective. You do not want to blindy turn it on for all 
repo on bitbucket.

So now simple4server.py includes a config switch to disable the 
capabilities to exchange obsolescence server side.

   [__temporary__]
   advertiseobsolete=False

The default is still "true" so you want to set it to False in your 
global config. And offer a check box to enable it in the repo config (as 
you did for publishing repo).

At some point mercurial core will have a descent strategy for exchanging 
the markers. We'll be able drop this option and enable it for all repo 
at that point.  Ihope to make quick progress regarding obsolescence 
exchange in the next few months.

Ping me if you have any additional question.

-- 
Pierre-Yves David