[M3devel] m3 CVS?
Jay
jay.krell at cornell.edu
Thu Mar 26 03:08:00 CET 2009
> > svn is at least somewhat better than cvs.
>
> In http://gravityboy.livejournal.com/39755.html, gravityboy says
>
> : I'm really tired of people pushing the adoption of svn because it's a
> : better CVS. The only people who that argument hasn't swayed are those
That's ambiguous to me.
He isn't clearly opposed to adopting svn over cvs, but svn over anything else.
It doesn't matter what I think, but I'm definitely not opposed to monotone.
Its marketing material reads among the best (seriously).
I'm not volunteering to do any conversion, and I'm sure I (and others) will grumble no matter how painless switching clients is, but I'm pretty sure there are gains to be had and ignore at least my grumbling.
I really don't like the web interface to CVS in particular. It doesn't let me identify "change sets" and view their diffs, I have to root around to all the files. Tinderbox does address this, on the side. (You would have to be sure, whatever replacement/conversion, included a web interface, anonymous read-only access, Tinderbox-or-other interop, etc.; imho you don't have to deliver all at once.)
The source control systems that use "databases", which I think monotone does, do they interact poorly with backup (in particular, whatever backup Elegosoft uses)? You know -- an incremental backup system that looks at file times/sizes would end up always copying the entire thing. Even so, "databases" can be a good thing..
I understand that "two way migration" lets people keep using either system, but I'm not sure that's worthwhile. On the other hand, if "the new way" is read/write, and a "cvs mirror" is read only, except for some blessed mirroring server, that should be fairly easy and have some value. That can also be a way to ease the transition wrt anonymous read-only access, Tinderbox interop, etc.
- Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090326/41ab5e44/attachment-0002.html>
More information about the M3devel
mailing list