On Thu, 2005-07-07 at 11:02, Patrick Mauritz wrote:
> On Thu, 2005-07-07 at 09:44, Darren Kenny wrote:
> > CVS and SVN were designed with globally spread out developers in mind -
> > TW wasn't. I think
> > this is what makes them stronger candidates as a code management system
> > for OpenSolaris.
> they still require developers to either have write access to the main
> repository
> and put all their files there or make a big mess with creating a new
> repository for
> local files and merging between them every now and then.
>
> please consider the (slightly newer) crop of tools that support really
> distributed
> work, eg. arch/bazaar, monotone, svk (there are more comprehensive
> lists, eg.
> http://www.venge.net/monotone/others.html)
>
> (summary of scenarios where distributed tools help and cvs|svn do not:
> - managing integration branches of some sorts, eg. Solaris (vs.
> opensolaris)
Should be easy with SVN.
> - helping those people on the plane or some island with slow net access
> still work
> reasonably fast, by having a local storage to put their changes in
> instead of
> waiting >1 minute for each commit - sync can happen later, after work
> where waiting
> is not an issue or when getting fast net access again.
Should be _really_ easy with SVN.
Hm, why do you think svn wouldn't be helpful in these cases ?
In fact that plane scenario is what I did a couple of weeks ago.
I used my SVN working copy to hack a bit PPC tree. So, yo must
be talking about something else then ...
Regards,
Cyril
_______________________________________________
opensolaris-discuss mailing list
[email protected]
