[OT] Q: what would you choose for a VCS today
Heiko Wundram (Beenic)
wundram at beenic.net
Thu Jan 31 01:24:41 PST 2008
Am Donnerstag, 31. Januar 2008 10:03:22 schrieb Julian Elischer:
> I'm having to use mercurial.
> I'm not really enjoying it.
> works ok for small projects. BSD is a bit big for it.
> doe work foe offline editing, but loses all your BSD history.
We're using mercurial pretty much for all of our (100,000+ SLOC) repositories,
and I cannot agree that it's only appropriate for small projects. As
mercurial is a distributed RCS, the hard part in using it is you have to
impose some policies, esp. related to merging changes back into a "central"
repository, which aren't required for "centralized" systems like CVS and
subversion, but from my view, the added benefit for a developer in using a
distributed revision control system is well worth the extra effort in writing
(and thinking) up the policies once. mercurial (at least by default) doesn't
allow you to create remote branches anyway (in pushing back changes to the
central store), so the policies you might have are effectly enforced by the
YMMV, of course, and mercurial has its defects (primary checkout/cloning of a
large repository from a central store takes ages, at least over a slow link,
the last time I had to do this [but I don't know if any progress has been
made there]), but for me, it's been working fine for the daily needs I have
as a developer.
Product & Application Development
More information about the freebsd-hackers