news from the topic experiment

Long Vu at
Tue Sep 27 11:44:31 EDT 2016

On Tue, Sep 27, 2016 at 8:19 AM, Pierre-Yves David
<pierre-yves.david at> wrote:
> On 09/24/2016 03:21 AM, Long Vu wrote:
>> I forgot a step.  The final "release" is a push to master, followed by a
>> push to the fork to propagate the public phase to the fork.  Is phase
>> propagation what you meant?
> I mean obsolescence marker propagation. Do you have enabled on either of
> your central repository ?

I only enable evolve on the fork, not on the master.  I am using
Kallithea as the repo manager, not hgweb.

Both of us pull/push very frequently to the fork.

Have not observed anything weird with missing obsolescence marker
propagation, what symptom should we be paying attention to?

I would love to try Evolve on Bitbucket ... is Sean listening :D

>> Pardon my ignorance because I have not yet tried topic, but since evolve
>> + named branch already gave me what topic would provide, what makes
>> topic superior?
>> Why would I want to try it other than because I am curious?
>> Not saying it's not useful.  Just want to know what it brings to the
>> table.
> As topic is designed for feature branch you would get various small
> advantage that will smooth your experience out:
> - Simpler push: pushing new topic to your non-publishing repo do not
> requires --force (if the non-publishing repository have topic enabled).

Ah right, with named branch, I have to push with --new-branch each time.

> Pushing to your main repository also make the topic disappear without the
> need of an initial rebase.

True I have to rebase before releasing.

> - Simpler and less error prone rebase: Running `hg rebase` from your topic
> will automatically update it on the head of the 'default' branch. Without
> removing the topic information.

Also true, to keep the branch name I have to rebase with --keepbranch

> - Better command to work with your stack
>   + `hg topic` list you active feature branch. `hg topic --verbose` list
> various statistic`
>   + `hg stack` show your current stack an help you to move within it,
>   + `hg evolve --all` will always evolve all of your topic only.
>   + `hg next` and `hg prev` stick to your current topic.


Long Vu | Build Controller | Intelerad | +1-514-931-6222 ext. 7743


This email or any attachments may contain confidential or legally 
privileged information intended for the sole use of the addressees. Any 
use, redistribution, disclosure, or reproduction of this information, 
except as intended, is prohibited. If you received this email in error, 
please notify the sender and remove all copies of the message, including 
any attachments.

More information about the Mercurial-devel mailing list