I have to agree that the DVCS I tried (Hg and Git) all are quite...
let's be honest: crappy (on Windows). I also tried to work on my own
branches using git, I tried to do Wine syncs using a special Wine
branch in a local git repo. All failed, everything was non trivial,
and required a lot more work.
Subversion just works. Also, a git mirror is provided, so that when
the trunk is locked for some reason, devs still have an option to:
a) create their own branch in SVN, work in a branch, do anything they
like
b) create their own git fork, work in it, publish it, get famous/
blamed, anything they like
There are no restrictions really, especially having in mind that our
SVN repo is already clonable by everyone, so everyone can have 10+
years of ReactOS hard work on a DVD disk.
I don't really see any need to switch our VCS to anything else.
WBR,
Aleksey Bragin.
On Nov 29, 2009, at 1:49 PM, Timo Kreuzer wrote:
Hi,
I worked with TortoiseHg some time, I thought I could get used to it,
but to no avail.
From my experience, I can only say that almost *everything* is non
trivial or doesn't work Apart from the shitty interface.
I just tested the latest version again, it's completely
unintuitive, and
merging gave me even more conflicts than I would have expected with
SVN.
My experience with using a branch with TSVN is that there's no
problem.
Even merging hundreds of revisions from trunk to the branch worked
quite
well with rarely any conflicts and it's done with a few clicks.
We don't need a different versioning system, we need a better source
organisation. Independency of modules. Independency from the tools/
sdk.
That would also help with working on branches.
Just my 2 cents,
Timo
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev