On 1/15/07, Carl Karsten <[EMAIL PROTECTED]> wrote: > > I'd suggest making the changes in your branch, and then inviting us to > > test with your branch, before merging it in with trunk. > > well, my branch is all polluted with the hacks I thought were needed when I > was > trying to fix what turned out to be a problem with pymssql.py (the unicode > thing.) > > So how do I 'start over' with a fresh branch? > > And can I branch just the db dir?
You can (I don't know what the best practices are for this project) make a new branch. >From my experience iwht svn on other projects: - make a new branch, don't bother only copying a bit, just copy the entire thing. copies are cheap. - If you want to only see the parts you are working on, use switch. So, have your workspace use trunk. svn copy the trunk to your branch, use the switch command on the directory or files you want to work on. This way, when you do updates, you'll get whatever is having on the trunk in your local workspace, but still have your changes. Later, when you want to have other people test, I'm not sure what a good process is. Ask for suggestions. On the projects I was working on, I had an environment where it was easy to do testing (unit, box, integration, etc) so I felt more confident about merging to the trunk without inadvertently breaking things. -- sheila _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
