Mercurial
Christian Vetter
SVN is not the best of all SCMs. Therefore I want to move MoNav to a
distributed SCM. The only alternative Google Code offers to SVN is
Mercurial, which is quite similar to Git. I already worked with it for
some months and I am pleased with it so far.
You can read about the advantages of distributed SCMs and other
features like three-way merges on http://hgbook.red-bean.com/ and
http://mercurial.selenic.com/ .
Does anybody have some objections against this change?
Regards,
Christian Vetter
Thomas Miedema
Christian Vetter
Since nobody dared to object I would propose we switch to Mercurial
directly after the 0.3 release.
Regards,
Christian Vetter
On Tue, Apr 12, 2011 at 9:16 AM, Christian Vetter
<veaac....@gmail.com> wrote:
Christian Vetter
I will switch to Mercurial sometime this weekend. Please refrain from
committing any changes to the SVN / Wiki until then.
Regards,
Christian Vetter
On Sun, Apr 17, 2011 at 11:44 AM, Christian Vetter
Christian Vetter
It seems as if everything worked out fine. The wiki is now hosted as a
separate repository ( wiki.monav ). You can still access the old SVN (
read-only ) at http://monav.googlecode.com/svn/ .
Some comments on working with Mercurial:
- As Mercurial is a distributed system you can commit changes locally
when working on something and you do not have to "push" it immediately
into the main repository. All your local commits will be visible once
you pushed to the central repository.
- From now on, if you work on a feature that require more than one
commit, you should create a new branch and only merge into the
"default" branch when the feature is in a "workable" condition. This
also has the added benefit that we can easily identify which feature a
commit belonged to (HG has some nice graphical tools). Small feature
can still be committed directly to the default branch.
Regards
Christian Vetter
On Sat, Apr 23, 2011 at 4:18 PM, Christian Vetter