Please don't reply to me, reply to the list. List convention is to *not* top-post.
On Tue, Oct 25, 2011 at 11:23, Robert J. Gebis <rjge...@gmail.com> wrote: > Ok so this is the only way to get around this problem? Well dumping and > reloading is another with rev range. > Does svnadmin tool support true "drop to revision". Or would it be possible? What's your goal? It sounds like you've already fixed the filename in the repository, so a checkout of HEAD (or any other revision that doesn't contain the bad filename) should work fine. Are you saying that this is not the case? Just don't check out/update to that particular revision on Windows and you should have no trouble. Where you're having trouble right now is the fact that your update with "aux" failed. Try svn cleanup on your working copy, if that doesn't let you continue then you'll need to do a fresh checkout. You''ll have to explain what "drop to revision" means if you want to pursue that. Doing major surgery on your repository right now seems excessive to me. > On Oct 25, 2011, at 9:48 AM, Andy Levy wrote: > >> On Tue, Oct 25, 2011 at 10:42, Robert J. Gebis <rjge...@gmail.com> wrote: >>> I did run into a problem that I was no aware of and I want to bring this up >>> to attention. Also I would like to know what is the best way to handle such >>> case since it gave me little problem. >>> >>> I am developing multi platform system. When I try to add "aux" folder on >>> linux I was able to commit just fine. Now wen getting update on windows I >>> was getting strange error saying that aux folder can't be created. Googling >>> I found below link explaining reserved words on windows. >>> >>> http://www.blindedbytech.com/2006/11/16/forbidden-file-and-folder-names-on-windows/ >>> >>> Now I try to move aux to misc on Linux and committing it. That was fine but >>> still on windows I was not able to get latest. >>> It looks like it was updating all changes and (creation of aux) before >>> applying (move aux mic). >>> I try to delete misc on linux and committing it. Still windows was >>> complaining. It does not seems like svn have true "drop" to revision. >>> >>> I ended up doing svnadmin dump -r 1:$GOOD_VER, created new repo and loading >>> it back. This is a long process. >>> >>> Are there any other/better alternatives. I was pressed on time so perhaps I >>> did overlooked something? >> >> A fresh checkout (instead of trying to recover the half-updated one >> from your initial attempt, when the file was named aux) should work >> fine. If you check out HEAD, the client should never see the file >> named "aux." > >