[Adium-devl] Version control

[Evan Schoenberg]

On Oct 8, 2007, at 2:54 AM, David Smith wrote:

> Almost
> no vocabulary commonality between it and svn

I've actually found very few differences between mtn and svn for  
vocabulary of the commands I use most.  The "monotone for cvs/svn  
users" guide does a good job showing what differences do exist.


> , 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"),

Unfair comparison; sync doesn't need that many arguments (you probably  
want to have the full db available) and would typically be used from  
within a checkout (so a database wouldn't need to be specified).  When  
doing a combined push/pull, mtn sync is sufficient once you're up and  
running, a one time process.

With the database checked out (which requires either doing a pull or  
downloading a bootstrap file from the server directly), the command is
mtn -d=$DATABASE_PATH co -b im.adium.adium local-adium-folder-name

vs

svn co svn://svn.adiumx.com/adium/trunk local-adium-folder-name

the only difference is that the path has been split into database and  
branch rather than including them both in a single URI.

> the output is
> somehow both more verbose but less useful (no, I don't care about the
> number of bytes that came in. I do, however, care about which files
> changed)
The bytes thing is indeed more info than I perhaps needed; that's just  
shown during a pull, though.  When updating, you get output identical  
to that of subversion.

> and things that used to be single step operations are often
> now two.

The only real case of this is commit / push and pull / update... and  
if you want to have local commits, a split in the work flow is  
necessary.

-Evan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20071008/a91d325d/attachment-0001.html>