Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Thanks Tony and Bo, We use that approach because of our branch policy (branch by change request). We cannot update the entire directory to a branch because developers often work with mixed working copies (two or more branches checked out in the same dir). Until we have add -r, how can I handle this situation? What server version you recommend for me to downgrade? Another doubt: The description you gave sounds like CVSNT branching model will be closer to subversion's model. Am I correct? What you said can be restated as something like: "it only makes sense to put a new file in a branch if the branch is the directory itself"? Because adding a new file means changing the directory file list. How CVSNT will manage directory revisions? I'm thinking that there is some kind of "impedance mismatch" between CVS branching model and the control of directory revisions. Thanks again Daniel Tony Hoyle wrote: > Daniel Lapolla wrote: > >> Tony, >> >> Can you provide a receipt for those who need commit -r to add new >> files directly into a branch? >> > For that case an add -r may be useful. commit -r is the wrong place to > do it (because it invites people to force files onto branches that > aren't supposed to be there). > > Even add -r is going to be the tiny exception - it isn't normal to put > isolated files onto branches that aren't part of directories. > > Tony