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

RE: Re: Cannot Checkout or Commit on New Repository

From: Gale, David <David.Gale_at_Hypertherm.com>
Date: 2005-11-30 21:46:53 CET

Hal Vaughan wrote:
> On Wednesday 30 November 2005 06:19 am, Ryan Schmidt wrote:
>> On Nov 29, 2005, at 19:56, Hal Vaughan wrote:
>>> and it imported all my files. Once this was done, I wanted to test
>>> it out, so I edited one program, /thresh/threshNet/bin/t-test by
>>> changing it just a little, and got this:
>>> [hal@server:threshNet]$ svn commit bin/t-test
>>> svn: '/thresh/threshNet/bin' is not a working copy
>> As Theo said, importing a directory into Subversion does not
>> transform that directory into a working copy. Theoretically, after
>> you import a directory into a repository, you then delete the
>> directory and check out a new working copy from the repository. In
>> practice you probably want to just move the imported directory aside,
>> in case you discover the import went awry and you need to redo it.
>> And in your case in particular, since you put the repository into the
>> directory you were importing, you certainly cannot delete it or you'd
>> delete the repository with it.
> I didn't realize or understand this, and it is an issue for me.

There're instructions in the FAQ
(http://subversion.tigris.org/faq.html#in-place-import) on how to do an
'in-place' import, such that the source becomes a working copy. Works
very smoothly, in my experience. I've used it several times, and will
probably continue to use it instead of import for any future projects I
need to set up.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 30 21:58:30 2005

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.