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

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

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-07-23 23:22:01 CEST

On 7/23/07, jbeall <jbeall.nabble@heraldic.us> wrote:
> I see this was requested back in the pre-1.0 days, but it doesn't appear to
> have gotten any interest since then... has the idea been abandoned? I would
> find it extremely useful. At my workplace we have *tons* of code that is
> not in a version control system of any kind, and it would be extremely
> useful to be able to do in-place imports. I can't imagine we're that
> unique--I've had too many conversations with devs at other shops that are in
> a similar situation.
> Import-Rename-Checkout works, but it would be a lot nicer to import things
> in place.
> Here's the issue link, and some of the details:
> 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.

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.

Mark Phippard
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 23 23:21:01 2007

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

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