Timothy J. Weber wrote:

>> It has atomic checkouts, file renaming (since you mentioned those two),
>> rather fine-grained ACLs (including on branches, so you can have a
>> development branch for all devs but not everybody can commit to the
>> production branch etc), exclusive editing for non-mergeable files
>> (which is something I need) and merge points (which is quite handy for
>> simple branching). 
> 
> I *think* Subversion has all those, FWIW (though I'm not sure what merge
> points are).  But still good to know.

Yes, I thought it didn't have anything like access control, but you showed
me something that does that. But I don't think this works on a branch
level, at least not the way you set it up. 

Similarly with the binary files... how do you handle, say, CAD files in the
repository?

Merge points are about the following... Say you have a main (stable)
branch, and develop a few features on separate branches off it. (May be
different developers, or not; doesn't matter.) If those feature branches
take a while, you want to regularly merge in the changes on the stable
branch. Merge points mean that the system remembers when you did the last
merge from the stable branch, so you don't have to. You just issue repeated
merge commands, and it always picks up from where you merged last. 

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist