List:Commits« Previous MessageNext Message »
From:Ingo Strüwing Date:July 19 2007 9:08am
Subject:Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909
View as plain text  
Hi Chad,

Chad MILLER wrote:
> 
> On 18 Jul 2007, at 12:57, Ingo Strüwing wrote:
> 
>> Chad MILLER wrote:
>> ...
>>> ChangeSet@stripped, 2007-07-12 15:11:49-04:00,
>>> cmiller@stripped +3 -0
>>>   Bug#26909: Specified key was too long; max key length is 255 bytes \
>>>       when creating table
...
> Would that change anything here?  This changeset is from last Thursday. 

I apologize. Don't know why I saw that one only after doing the review.
Perhaps I didn't wait long enough for my mail reader to find more emails
 for this bug. Again I learn that working quickly has a high risk for
mistakes.

OTOH I'm not yet used to expect a "burst" of changesets instead of a
single one.

Regards
Ingo
-- 
Ingo Strüwing, Senior Software Developer
MySQL GmbH, Radlkoferstr. 2, D-81373 München
Geschäftsführer: Kaj Arnö - HRB München 162140
Thread
bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Chad MILLER12 Jul
  • Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Ingo Strüwing18 Jul
    • Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Chad MILLER18 Jul
      • Re: bk commit into 5.0 tree (cmiller:1.2503) BUG#26909Ingo Strüwing19 Jul