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

Re: Checkout to same directory after import?

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-10-04 20:58:42 CEST

On 10/4/06, Ryan Schmidt <subversion-2006d@ryandesign.com> wrote:
> On Oct 3, 2006, at 16:21, Ron Olson wrote:
>
> > I have added a directory containing some files to Subversion ( 1.4)
> > so that they are now under source control. Without deleting and
> > recreating the folder, I would like to now "get" them insofar as I
> > don't really want to get them again, I just want to have Subversion
> > create the .svn directory as if I did. I have made absolutely no
> > changes so the files should be identical.
>
> The responses you've already received describe an alternative to "svn
> import" that you can use to get the files into the repository
> initially and have your directories automatically transformed into a
> working copy.
>
> If you have already used "svn import" and everything's already in the
> repository, and you now want to have Subversion create the .svn
> directories in the directory you imported, then that's unfortunately
> not available in Subversion yet. Someone just posted a message on the
> list a week or so ago about how this feature (where you can force a
> checkout on top of an existing directory filled with files) might
> make it into Subversion 1.5, but I cannot find the message now.
> (Search terms fail me.)

That would have been my message about a --force flag for checkout
which transforms an existing tree into a working copy. This option is
in trunk now and will be included in the 1.5 release.

Hope that's what you're looking for?

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 4 20:59:34 2006

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.