[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] new feature: takeover

From: Norbert Unterberg <nunterberg_at_gmail.com>
Date: 2005-07-08 08:03:29 CEST

2005/7/8, Jonathan Gilbert <o2w9gs702@sneakemail.com>:

> Anyway, I'm happy to see someone else who agrees with me that redoing a
> working copy from scratch, including manually copying over edited and
> unversioned files, is annoying and that even if it means re-downloading
> everything from the server, automating the process is worthwhile :-)

I fully agree. I see two other cases where I would have liked this feature:

* Create a new project in the repostory from an existing directory tree:
This can be done by svn import, but then your tree is not a working
copy. You need to delete (or rename) the tree and then do a fresh
checkout. With takeover, I would just run an svn takeover on the same
folder an I am done. I don't care about the double download, we are
working on a LAN.

* Sync a SVN wc with CVS.
This was done in our company when we started migrating from CVS to
SVN. I created a folder that was a WC for both SVN and CVS, by copying
a SVN WC over into the CVS WC. It would have been much easier to do a
scn takeover on the CVS working copy!

Question: Since takeover and checkout are very similar, why creating a
new "svn takeover" and not a "svn checkout --force"?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 8 08:04:35 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.