> I've encountered a problem using TSVN 3840. Most probably because I
> don't fully understand reverts yet. Here is the most simple example to
> recreate my problem (revisions shown in brackets).
> create a fresh repository and checked it out to an empty directory
> (1) create a file: notes.txt with some random text, add it and commit
> (2) delete notes.txt and commit
> (3) create a file: notes.txt with some random but different text, add it
> and commit
> now i decided i wanted to revert back to revision 1 with the original
> file, so i brougt up the log and selected revisions 2 and 3 and clicked
> "revert changes from these revisions". This successfully restored
> notes.txt to what it was in revision 1.
> However, now i can't do anything to the working copy. If i try to commit
> I get the "out of date / update working copy first message." If I follow
> that advice and try to update i get the error "working copy path
> 'notes.txt' does not exist in repository". If I select revert, it will
> clear the modified icon on the file, but I am still unable to commit or
> update my working copy.
> How do I get out of this state?
Hmmm. This looks like a bug in subversion. It happens with the command
line client too.
As an aside, TortoiseMerge hangs with 100% CPU if you try to diff the
file after using this revert method.
Sorry to say the only answer is a fresh checkout.
> (Incidentally, the issue track lists
> http://tortoisesvn.berlios.de/issues/?do=details&id=220 as being
> implemented in 5803 but under 5840 I can not find the "revert to this
> revision" menu item in the log browser)
That's because issue 220 was implemented on trunk, not on the release
branch (which contains only bugfixes). It will be available in 1.4.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 10 12:14:50 2006