I just fixed your r172 log message -- the 'svn:log' revision-property was illegal.
The subversion repository doesn't allow control-characters in log messages, and somehow the git-svn tool allowed a bad character to slip in. Granted, the server probably ought to enforce this restriction, but I think historically the subversion libraries themselves have always reject log messages that have control-characters in them. Either git-svn is being a "bad" svn client by allowing them, or it's using a *really* old svn commandline tool. In any case, I deleted the svn:log revprop on your r172, and then re-created it without the control character. All is normal again. On Fri, Dec 19, 2008 at 1:00 PM, Andrea Del Signore <[email protected]> wrote: > > Hi all, > > sorry to bother, but today I think that I broke the svn repos of one > project of mines. > > The project url is: http://vtg.googlecode.com > > And I broke it with (I think) a problem caused by the git-svn tool > that I use to track the svn repos. > > Now a git clone stop the downloading at revision 171, and what is > worse is that an svn log list just revision 173 (which is HEAD). > > So I tryed to do an svn log -r 172 and all I get is: > > and...@cipi:~/Documents/src/vala/vtg-git$ svn log > https://vtg.googlecode.com/svn/trunk > -r 172 > svn: REPORT request failed on '/svn/!svn/bc/172/trunk' > svn: REPORT of '/svn/!svn/bc/172/trunk': 200 OK (https:// > vtg.googlecode.com) > > I don't know how to proceded, and I hope that I can do something to > recover from this situation. > > Thanks for all the help. > > Regargs, > Andrea > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
