List:Commits« Previous MessageNext Message »
From:Guilhem Bichot Date:January 19 2011 6:58pm
Subject:bzr commit into mysql-next-mr-bugfixing branch (guilhem.bichot:3260)
View as plain text  
#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?


Attachment: [text/bzr-bundle] bzr/guilhem.bichot@oracle.com-20110119185853-i7s0wp4vtf181t3g.bundle
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