Paul McNett wrote:
> Carl Karsten wrote:
>> Paul McNett wrote:
>>> Ed Leafe wrote:
>>>> Reverted the changes committed last night until they can be tested and 
>>>> shown to be working for all cases.
>>> Carl: I think you are on the right track, as we really should be letting 
>>> the backend db handle the parameters. However, it is a large change over 
>>> how we were doing it before, so it did warrant some discussion and 
>>> agreement before just doing it.
>>>
>>> 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?
> 
> Carl, what about just making another branch?
> 
> svn copy http://svn.dabodev.com/dabo/trunk 
> http://svn.dabodev.com/dabo/branches/carl2
> 
> It is always better to copy the whole project (don't worry, the copies 
> are really cheap: they don't result in actual copies on the repository 
> side, just symlinks), although you could branch just the db directory if 
> you wanted to (but how would you easily test before merging with trunk?)
> 
> Or if you are all done with your current branch and you aren't going to 
> lose anything important, clean it up before creating your new branch:
> 
> rm -rf carlbranch
> svn up
> svn remove carlbranch
> svn ci

Ok.  The work I did turned out to be just workaround fluff.  completely useless 
once pymssql.py was fixed.  (thanks again John.)  I can see the value in 
revision history of stuff that actually works, but not some wild goose chase.

Carl K

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev

Reply via email to