«mercurial for dummies»: topic-mode = random-all does not prevent abort: push creates new remote head f4ac423831b6

[Uwe Brauer]

Hi

This is to continue the discussion «mercurial for dummies».
As I understand Pierre Yves, maybe not correctly
Putting 

[experimental]
topic-mode = random-all

Should avoid the abort: push creates.


I just run a test and it does not.

Here is what I did 

 mkdir Server
 cd Server
 hg init
 echo "First" > test.org
 hg add test.org
 hg commit -u "Bernhard Riemann <bernhard.riemann at gmail.com>" -m "First"
 echo "Second" >> test.org
 hg commit -u "Bernhard Riemann <bernhard.riemann at gmail.com>" -m "Second"
 echo "Third" >> test.org
 hg commit -u "Bernhard Riemann <bernhard.riemann at gmail.com>" -m "Third"
 echo "Forth" >> test.org
 hg commit  -m "Fourth"

 cd ../
 hg clone Server Ben
 hg clone Server Uwe

Adding 
[phases]
publish = False

 to each local repository (just in case)
 cd Ben
 edit
 hg ci -m "Test"
 hg push
 cd ../Uwe
 edit
 hg ci -m "Test topic"
 hg push

And voila I obtain 

searching for changes
remote has heads on branch 'default:brazen-cattle' that are not known locally: ea7b0e082a8e
abort: push creates new remote head f4ac423831b6 on branch 'default:brazen-cattle'!
(pull and merge or see 'hg help push' for details about pushing new heads)


So the situation is not different of not having used 

topic-mode = random-all

What do I miss?

Regards

Uwe Brauer