无法在Windows服务器上物理上找到svn目录

Question

I have just successfully installed the subversion in windows server 2008 i can checkout the directory from my client machine svn://ip/test but i am unable to locate test directory on server.

Repository in F:\\SvnRepository and conf folder in F:\\SvnRepository\\conf and binaries are in C:\\Program Files (x86)\\Subversion
Created directory by executing the command svn mkdir svn://localhost/test .

Answer 1

The svn repository cannot be used like a working copy. Simply check out the repository to a working copy somewhere (with svn checkout - you already did that at least once).

Also, note that using svn mkdir with a URL is an unusual command. Typically, you create the local changes (including new directories) in your working copy (on the client) and then commit them.

Answer 2

If you used the "svnadmin create " normally it is being created at your

system32 folder [ C:\\Windows\\System32 ].

Answer 3

You can use svn mkdir but it's a bit awkward methods. I use this method only when i really need create a structure online because i don't want to checkout everything. For example:

svn mkdir http://myserver:81/svn/CatalogRepo/newclientcode/
svn mkdir http://myserver:81/svn/CatalogRepo/newclientcode/web/
svn mkdir http://myserver:81/svn/CatalogRepo/newclientcode/web/trunk/
svn mkdir http://myserver:81/svn/CatalogRepo/newclientcode/web/branches/
svn mkdir http://myserver:81/svn/CatalogRepo/newclientcode/web/tags/
svn co http://myserver:81/svn/CatalogRepo/newclientcode/web/trunk/

and then start working with with the new checkedout trunk. Note too, that you only do that if you already got something in http://myserver:81/svn/CatalogRepo/ for example... if the repo is clean, just check it out locally, create your folders, publish the changes ALL AT ONCE and then delete and checkout again the trunk this time.

The creation of directories directly on the server forces you to create a revision everytime you send a command while checking out a directory and doing everything locally allows you to do one big commit, it's much better that way!