Hello there. We generally consider repository resets to be a Bad Practice. There are typically only three legitimate reasons for resetting a repository:
1. Something really sensitive, confidential, or illegal was accidentally committed, and now exists in the history forever. 2. Some huge garbage was accidentally committed, and now a ridiculous amount of disk quota is wasted. 3. A project owner wants to replicate a prior repository into the repository using the 'svnsync' tool (which requires an empty repository at revision 0). Can you let us know why you need the repository to be reset? If it's not for one of these three reasons, our recommendation is to simply "svn rm" data in the latest revision, so that your filesystem appears to be empty again. This still gives you a clean start in terms of repository organization, but without losing the older data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
