Milan Cermak wrote:
Hi all,
being used to Subversion and CVS, I come over Mercurial. Looking at its
ways of working, I can't understand what is the distributiveness for and
why should I replicate whole repository with all its history just to
change few files.
So what is the benefit of having distributed repository?
on-gate moving a long with bug fixes and new projects
project gate for big thing say zones is a child of onnv-gate
project gate for big thing say dtrace is a child of onnv-gate
project gate for big thing say cryptoframework is a child of onnv-gate
Both of those projects have more than one developers putting stuff into
the project gate. The project gate is periodically resync'd with on-gate.
Some time before either of zones,dtrace,cryptoframework are due to
putback they want to cross sync, an engineer in the crypto group needs
to work on a zones/crypto problem and needs dtrace to help out debug it.
If you don't use a distributed SCM system you can't do that 3 way sync
that easily.
Oh BTW I really did do that 3 way sync during the development of Solaris
10 as did many other engineers working on projects that went into
Solaris 10 and as do engieners still today do those kinds of cross
project pre-integration merges. For Solaris 10 we did this with
Teamware which is also distributed.
In an opensolaris world this becomes even more important.
--
Darren J Moffat
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
