Re: [XMLPipeDB-developer] GM Builder post taxon merge

[John D. N. D. <do...@lm...>]

Hi Rich,

I think it's OK to commit to the trunk, with one tweak for easy management: before committing, copy out ("tag") what is in the trunk right now, and put it in /tags/gmbuilder/before-name2taxon-merge (or something like that).  This way, you have an easy basis for comparison if you need to go back to how the trunk was before name2taxon came along.

Also, it will save some time if your before- and after- .gdbs are available.  Running our own exports, while of course doable as you said, would require things like getting old versions, building them, etc.

Happy digital forensics...

John David N. Dionisio, PhD
Associate Professor, Computer Science
Loyola Marymount University


On Apr 1, 2011, at 11:42 AM, Richard Brous wrote:

> Hi all,
>  
> Started a new thread since this is Pfalciparum specific.
>  
> I have double checked my manual merge to confirm that in fact my edits were correctly included for Mtuberculosis and Pfalciparum.
>  
> So when running gdb exports for each I determined that in fact something broke in the merge.
>  
> Before I start digging into this further I want to ask a couple questions:
>  
> 1. Should I commit the changes up to Sourceforge yet or leave them locally on my laptop while troubleshooting? I know we can revert to earlier versions if needed but wanted to be sure we were all on same page.
>  
> 2. I have before and after exports of Mtuberculosis and Pfalciparum on my laptop. Would you like me to post them for review or will you be running your own anyway?
>  
> Richard
> <ATT00001..txt><ATT00002..txt>