On 12.05.06 17:49:35, Mark Gibson wrote:
> so if i do svn revert doc again at least it gets me in a state where i can do
> commits. but is there someway i can actually delete that doc directory?
> sourceforge website seems to be down, so i couldnt go through there svn viewer.
> but i moved the doc directory and did a svn update to see if in fact it would be
> updated - and it was - i got an empty doc directory. not the end of the world
> but it would nice to delete.
>
> oh actually i got it. after the moving and the updating, i then did a delete and
> it was gone, so i mustve got it in a funky state and the mv & update helped
> restore it somehow. thanks for your help, mark
I doubt you got the exact same error, if you did I'd try to find another
hoster. The error message looked like a "broken" ssl-connection, not an
error from svn. Subversion would've told you that the current directory
is not "up-to-date" and thus you cannot commit it.
This is the way of subversion, if you make changes in directory dir1
(for example removing dir2 contained in dir1) and commit these you need
to run svn update in dir1, because you've got mixed revisions in dir1.
In fact all other items in dir1 are still the "old" revision where dir2
was present but the latest repository revision is old+1, due to
subversion using global revision numbers. And as the whole workflow of
subversion is based upon committing after an update, so you got all the
latest changes in the repository you need to do an update here.
Hope that clears things up, so often it's just a good idea to do an svn
up after an svn commit.
Andreas
--
Is this really happening?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 13 03:17:08 2006