Gerhard Fiedler wrote:
> Timothy J. Weber wrote:
> 
> 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. 

Sure.  It's just that, in Subversion, branches are normally placed in a 
different path, like this:

/myproject
  /branches
   /newfeature
  /tags
   /release1.0
  /trunk

So I think you could assign different permissions to each of those 
locations without a problem.

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

Binary files don't require anything special in Subversion... they're 
diffed using a binary diff algorithm, and the binary diff is what's 
stored and transmitted.

Is that what you mean?

> 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. 

Hm... I don't do that a lot, so I'm not sure... but Subversion 
lets/makes you "resolve" changes against a given revision before 
committing them, and I think it does remember what you last resolved to. 
  So I think you can resolve but not commit, and then resolving again 
later will do what you're talking about.
-- 
Timothy J. Weber
http://timothyweber.org
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist