At 01:33 PM 21/04/2006 -0400, you wrote:
>Jonathan Gilbert wrote:
>> ...
>>> equivalent of a checkout in that directory, e.g.:
>>>
>>> svn import --takeover http://foo.bar.com/myproject/trunk
>>>
>>> to import the current directory or:
>>>
>>> svn import --takeover myproject http://foo.bar.com/myproject/trunk
>>>
>>> to import the named directory and setup a WC there.
>>
>> This is completely the opposite of the original reason I designed the
feature.
> > ...
>
>OK, I've read your post, and I don't understand why this would be
>"completely the opposite". My suggestion for an import option would
>be equivalent to doing a checkout with option or a new takeover
>command after the import.
>
>In short, why not provide an option to import that is a shortcut for
>a (relatively) common use case?
As I said before, "svn import"'s main function is to add files to the
repository when the local copy is not a WC. The function of "svn takeover"
is to turn something that is ostensibly a working copy, just not one that
Subversion knows about, into an official SVN working copy without sending
anything to the server. In fact, the latest revision is *retrieved* from
the server, in order to build the text-base.
Are you suggesting that "svn import --takeover" would *not* commit a new
revision to the repository?
Are you talking about a separate feature here that would automate the
process of "URL=svn://... (svn import $URL && svn takeover $URL)"?
If it is the latter, then I apologize, because I (mis)read your original
post as suggesting an alternate place for the takeover feature, to the
exclusion of it having its own command (or flag to "checkout" or what have
you).
Jonathan Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 21 22:10:48 2006