I'm really lost as to what you're trying to accomplish, probably because you're being sloppy with terminology and/or don't understand how subversion works. That said, the confusion isn't your fault -- you shouldn't have to be an expert at this stuff. :-)
>From where I sit, here's what I see: 1. You created a new pykata project with an empty repository. 2. You used 'svnsync' to copy all 60 revisions from the old pywhip repository to the new pykata repository. 3. Since then, you've committed 5 new revisions to the pykata repository. I see nothing suspicious on the server or with the new pykata repository. I suspect all the frustration is coming from confusion around client-side manipulation of your working copies and uncommitted changes. My suggestion isn't that you "start fresh" by nuking the repository -- you should nuke your *working copy* and do a completely fresh "svn checkout" of the pykata project. The fact that you're messing around inside .svn/ folders means you've probably corrupted the whole working copy -- .svn/ folders should never be touched, ever. Just do a fresh checkout to a new folder. Try making a simple change and committing that change. Then move forward from there. If there are modified files in the old "dead" working copy, then carefully copy them on top of the new working copy, so that it appears like you've edited them in the new location. Then you should be able to commit. -- You received this message because you are subscribed to the Google Groups "Project Hosting on 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.
