>
> There is such a tool. It's called the repository.
>
> > I've been in situations where subversion has gotten
> confused with an
> > added folder, and the end solution was to delete the entire working
> > tree and checkout again, with a fair amount of copying
> local files to
> > and from a temporary directory.
>
> If you had committed your work after every each change worth
> saving, a fresh checkout would be an easy solution, not just
> for you, but for anyone else working on the code, or to let
> you pick it up on a different machine. If you have a 'clean
> trunk' policy where someone is bothered by work in progress
> there, copy to a branch for the intermediate work and merge
> it back when appropriate. The point of a revision control
> system is that you put your revisions in there.
>
> --
> Les Mikesell
> lesmikesell@gmail.com
>
Thank you Les, I am obviously a n00b luser and shouldn't be allowed
access. <sigh>.
Anyway, my problem is NOT one of committing changes. Its of creating a
new folder inside an existing svn-controlled folder. I have a root
project that contains several sub-projects (a admin tool, runtime server
and 3 plugins) and my problem arose when I tried to add a new plugin. I
started by copy-pasting an existing one before editing it, and forgot to
delete the hidden .svn directories. And that is when the problems
started. I could not add them, commit them, copy them, clean the folder
up or anything other than scrap it and start again.
Now, I don't mind if I delete the .svn directory and have to restore the
link to the repository, that's obvious even to me, but I would really
like the subversion tools to recognise that I'm fallible and that bad
things happen to the working copy .svn directories and provided a
solution to help me resolve these problems easily.
Don't forget that you may find these problems *when you come to perform
a commit* more often than not, because until then, you do not even
realise your .svn directories have been trashed. (not that this applies
in my case, as I had nothing in the repo *to* commit yet).
It has nothing to do whether it was my fault, or subversion's fault. I
only care about being able to fix it easily and without fuss. As other
people have pointed out, the WC is pretty fragile, so this cannot be an
issue for a few people. Making it more robust isn't practical (or even
possible?) so the next best thing is to provide tools to make repairs.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 7 10:38:53 2007