Reorganization of the project after checking SVN

This is probably SVN 101, but I have to ask:

I am working on a project that has some chronic directory structure. To run it and run in my favorite IDE, after I checked the project, I copy the whole project to another directory and move things to my liking (and my IDE).

So my main question is: can I safely edit / update / merge a file that is in a different strcuture directory than the repository directory structure?

For example, if I check /home/me/dev/proj/index.jspand then copy it (and its metadata .svn) to /home/me/dev/better-proj/web/index.jsp, then the fact that index.jsp is in another directory should be in order with its SVN status, right? Wrong? Or am I just asking for trouble?

+5
source share
5 answers

You ask for trouble. A lot of trouble. If you try to update the root, as a result you will get complete insanity (many obstacles, "restored" files, etc.). Also, how do you copy the metadata of a single file? SVN metadata is stored in the .svn folder, which is located in the directory. You may be able to update and commit individual directories that have not been changed (i.e. the directory itself has been moved or renamed, but all its children are exactly the same as in the repo). Again, you cannot. This is dangerous.

IDE, , /, , , /. svn move (.. svn help move). , GUI SVN, TortoiseSVN ( ), .

+6

, svn move (). , .svn , .

, svn export () repo, svn add () .

: Subversion

+2

, , ? , . svn: , , .

+1

, , . , -, , .

, svn move ? , .

+1

. , - SVN. (. )

, -, , .

, . . svn?

0

All Articles