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). If you're simply trying to "delete the mess", our recommendation is to just "svn rm" all 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. -Mike On Feb 20, 10:56 am, wingrunr21 <[email protected]> wrote: > Can I please have SVN reset for the OSXBGE project > at:http://code.google.com/p/osxbge/ > > All source has been backed up. The code hosted there is unworkable in > its current form and I would like to start fresh. Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
