Sounds quite reasonable to me. I don't think my old company will have much time or resources to devote to reviewing this right now, but they might come back to it someday. This sounds like a good way for you to move forward and maybe it will ease things for them later.
Chris Jess Robinson wrote: > > Thanks for replying Chris, I was hopiing you would ;) > > Hmm, I was pondering having it take an --old-compat parameter or > something that would use the old code.. But on second thought, how > about if I revive the sqlt-diff from before the split into a module, > and check it in as sqlt-diff-old? I can then put warnings in the new > one, that point to the old one, in case of compat problems.. > > Does that seem sane? > > Jess > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- sqlfairy-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlfairy-developers
