[Adium-devl] Version control

[Chris Stewart]

Just to put my 2 cents in...
I like the idea of a DVCS.  I watched the git presentation on Google Video
not too long ago and it appeared worthwhile for distributed open source
projects like Adium.  However, Linus isn't exactly a great presenter, so
some of the actual usage points were lost in favor of attacks on CVS and SVN
the entire time.

I'm as open to a new software tool as the next guy.  However, I would
carefully consider these options in moving your code repository.  As you all
obviously know, your repository is a key factor in the management of your
project.  If a move is made, I would suggest a decent amount of
documentation on how to utilize this tool for working with your repository.
 Along with detailed documentation to demonstrate how to take advantage of
the new capabilities this tool provides.

Chris


On 10/8/07, Richard Laager <rlaager at wiktel.com> wrote:
>
> My apologies for this being a reply to the wrong part of the thread.
> Everyone: Please use "reply to all" in the future to include everyone.
>
> On Oct 7, 2007, at 11:54 PM, David Smith wrote:
> > Almost
> > no vocabulary commonality between it and svn
>
> I've already mentioned the CVS phrasebook, which should help a lot.
>
> > , most of the commands
> > appear to be significantly more complex/less readable (say, mtn --
> > db=abe.mtn sync jim-laptop.juicebot.co.jp "jp.co.juicebot.jb7*" vs.
> > "svn checkout svn://svn.adiumx.com/adium/trunk")
>
> This isn't really a fair comparison for a number of reasons.
>
> The first time, you have to download a database. This is unfortunately
> far *more* painful than SVN, as MTN doesn't support shallow checkouts
> (i.e. retrieving just the head as you do in SVN). See the example:
>         http://developer.pidgin.im/wiki/UsingPidginMonotone
>
> MTN will save the server and branch pattern in the database. So, after
> that initial bootstrapping, which is the typical developer case, you're
> really talking about running "mtn pull" * from a working directory
> instead of that huge "sync" command.
>
> * or "mtn sync", depending on your preference and how you intend to
> handle merges -- a sync is just a push and a pull together
>
> So these comparisons are:
> svn commit
> vs.
> mtn commit ; mtn push
>
> AND
>
> svn update
> vs.
> mtn pull ; mtn update
>
>
> > , the output is
> > somehow both more verbose but less useful (no, I don't care about the
> > number of bytes that came in.
>
> Yes, this is more verbose than you probably need. Passing --quiet should
> take care of that. I'm not sure if there's a way to set that by default,
> but there probably is.
>
> > I do, however, care about which files
> > changed)
>
> This is something that goes with update, not with pull.
>
> > and things that used to be single step operations are often
> > now two.
>
> Yes, this is a change. It means a few more commands, that's true. It
> also allows for different workflows.
>
> Richard
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
>


-- 
Chris Stewart
cstewart913 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20071008/373a8c67/attachment-0001.html>