Opps... sorry Paul... also meant to forward this to dev mailing list
Paul Burba [mailto:firstname.lastname@example.org] wrote:
> The code was committed to trunk in early August. It's not called takeover
> anymore - you can dig through the threads on "takeover" if you are curious
> about the gory details as to why http://svn.haxx.se/dev/...
> ...But at the moment the 'functionality-previously-known-as-takeover' is
> implemented with the --force option for svn checkout, update, and switch.
It makes more intuitive sense to add a switch instead of another verb.
> Support --force option with svn checkout, update, and switch.
> With the force option, co, sw, and up now tolerate unversioned
> obstructing paths when adding new paths of the same type, rather than
> generating a SVN_ERR_WC_OBSTRUCTED_UPDATE error.
> If the obstructing path is the same type (file or directory) as the
> corresponding path in the repository it will be left 'as-is' in the
> working copy. For directories this simply means the obstruction is
> tolerated. For files, any content differences between the obstruction
> and the repository are treated like a local modification to the
> working copy.
If my vote counts for anything as a user, then +1.
> If that isn't clear let me know and I can clarify further.
> > Do you know what feature release it might be deployed in (1.5 or 2.0?)
> 1.5 is the plan, but before you ask, I don't know when that will be :-)
> Hope that helps,
Thanks a lot for the info. I appreciate the clarity. I've been following
the list for over a year now so I have an idea how long this might take. ;)
The takeover / forced checkout / whatever you want to call it feature will
help a lot since some of the changes that I make happen in a live
environment. I'd sooner just do the initial import in pre-production where
everything is working then a forced checkout in both pre-prod and production
without having to blow away folders and re-create user/group permissions on
those files just so I could have a working copy in place for future updates.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 15 16:21:15 2006