news from the topic experiment

Long Vu at
Fri Sep 23 12:08:58 EDT 2016

On Fri, Sep 23, 2016 at 11:50 AM, Long Vu < at> wrote:
> I emulate git lightweight branching by basically using named branch
> with evolve and working on the fork of the "master" repo.

We only enable evolve and non-publishing on the fork repo to make sure
we can not alter history on the master repo where the releases are
coming from.

We have one bug/feature per branch on the fork repo so it's very easy
to manage when we have many concurrent bugs/projects to juggle.

Since we push often to this fork repo, it's like having backup of the
work on our machine and taking last minute day off is easy because the
other person have all the latest code to continue the work without
having to hunt where we store that ongoing work on our machine.

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