List:Commits« Previous MessageNext Message »
From:Davi Arnaut Date:January 19 2011 7:08pm
Subject:Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)
View as plain text  
On 1/19/11 4:58 PM, Guilhem Bichot wrote:
> #At file:///home/mysql_src/bzrrepos_new/mysql-next-mr-opt-backporting-wl4800/ based
> on revid:guilhem.bichot@stripped
>
>   3260 Guilhem Bichot	2011-01-19
>        todo question
>
>      modified:
>        WL4800_TODO.txt
> === modified file 'WL4800_TODO.txt'
> --- a/WL4800_TODO.txt	2011-01-17 20:41:34 +0000
> +++ b/WL4800_TODO.txt	2011-01-19 18:58:53 +0000
> @@ -44,3 +44,7 @@ Make --opt-trace-protocol dump traces to
>   can run with it without failing all tests.
>
>   Update copyright header of all changed files to reflect changed in 2011
> +
> +should the debug binary really assert(0) if json syntax error? is it a
> +good idea at the customer's? On the other hand, how to make sure a
> +developer notices a syntax error when running tests?
>

Perhaps it is time for us to have a DEBUG_WARN?
Thread
bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260) Guilhem Bichot19 Jan
Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)Davi Arnaut19 Jan
  • Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)Guilhem Bichot19 Jan
    • Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)Davi Arnaut19 Jan
      • Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)Guilhem Bichot20 Jan
    • Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)Bjorn Munch19 Jan
      • Re: bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)Davi Arnaut19 Jan