Re: I would like to vote for issue 1328 -- in-place import feature request

Mark Phippard-3 wrote:
>
> On 7/23/07, jbeall <jbeall.nabble@heraldic.us> wrote:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=1328
>
> I am not even sure why that is still open. You can certainly do stuff
> like that today. If this is all new code, just create the folder for
> it in the repositry, then checkout that folder to the location where
> your code resides. You can then svn add + commit which will leave
> behind a working copy. This is even referred to as "In-place import"
> which is why I am surprised this issue exists.
>

Interesting; I had tried this already without seeing the FAQ (Nathan Kidd
referenced the FAQ for "in-place import" in a different reply), but I was
missing the "checkout" step. That was the key to getting a proper working
copy.

This all works and does exactly what I was hoping for. Thanks. However, I
do think it would be slick to combine this into a single "in-place import"
command of some type. Alternatively, perhaps TortoiseSVN (and/or other
tools) could provide one-click in-place importing, implemented via the
"create folder->checkout to existing folder->add->commit" method. Nothing
more than a convenience method, but convenience *is* nice!

Thanks for the pointers!

Mark Phippard-3 wrote:
>
> As of the next version, you can now even use svn checkout --force to
> checkout an actual code tree on top of another code tree. It will
> leave the files in place and slide the WC beneath it.
>

That will be a nice feature.

  -Josh

-- 
View this message in context: http://www.nabble.com/I-would-like-to-vote-for-issue-1328----in-place-import-feature-request-tf4132507.html#a11754239
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org