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

Re: AW: Re: Can I have the same folder in twice?

From: Gabriel Rossetti <rossettigab_at_charter.net>
Date: 2005-11-02 11:56:01 CET


Thank you, I understand things better now.


Paul Koning wrote:

>>>>>>"Gabriel" == Gabriel Rossetti <rossettigab@charter.net> writes:
> Gabriel> Hi Felix, Thank you, yes, indeed, that must be it. My
> Gabriel> question now is, how can I fix everything? I have been
> Gabriel> playing around with svn and I've made a mess, how can I get
> Gabriel> a fresh start? Where is all this working copy stuff stored?
> Gabriel> It's still not very clear for me. So there is a sort of
> Gabriel> "global" db somewhere to keep track of all this? I've used
> Gabriel> CVS some, but this working copy thing must be a new
> Gabriel> construct.
>No, "working copy" is also a CVS construct. You may know it by a
>different name; some people call it "sandbox".
>If you do this:
> cvs co something or svn co something
>then the result is a working directory (sandbox) named "something" in
>your current directory. That's where you do your work -- edit, build,
>test, and finally commit.
>In either CVS or SVN, a working directory points back to the
>repository it was checked out from. In CVS, say "cat CVS/Root" to
>find out; in SVN, say "svn info".
>The repository is the database where permanent work lives. It doesn't
>know anything about working directories; a checkout does not get
>recorded in the repository. For the most part, only commits change
>the repository.
>In CVS, a repository is known simply by its name. In SVN, a
>repository has a UUID, so if you delete it and create another one with
>the same name, CVS will think it's the same, and SVN will know it is
> paul
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 2 11:58:21 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.