On (29/07/16 11:44), Lukas Slebodnik wrote:
>On (26/07/16 15:00), Jakub Hrozek wrote:
>>Hi,
>>
>>please see the attached patches. I'm not sure how this bug got in,
>>because in the patch that broke the functionality
>>(eef359b508b898ae99d2bf292a43f0f295a2ba5e) I said in the commit message
>>that I
On Fri, Jul 29, 2016 at 03:08:52PM +0200, Jakub Hrozek wrote:
> On Fri, Jul 29, 2016 at 02:59:46PM +0200, Lukas Slebodnik wrote:
> > On (29/07/16 13:01), Jakub Hrozek wrote:
> > >On Fri, Jul 29, 2016 at 11:44:53AM +0200, Lukas Slebodnik wrote:
> > >> On (26/07/16 15:00), Jakub Hrozek wrote:
> > >>
On Fri, Jul 29, 2016 at 02:59:46PM +0200, Lukas Slebodnik wrote:
> On (29/07/16 13:01), Jakub Hrozek wrote:
> >On Fri, Jul 29, 2016 at 11:44:53AM +0200, Lukas Slebodnik wrote:
> >> On (26/07/16 15:00), Jakub Hrozek wrote:
> >> >Hi,
> >> >
> >> >please see the attached patches. I'm not sure how
On (29/07/16 13:01), Jakub Hrozek wrote:
>On Fri, Jul 29, 2016 at 11:44:53AM +0200, Lukas Slebodnik wrote:
>> On (26/07/16 15:00), Jakub Hrozek wrote:
>> >Hi,
>> >
>> >please see the attached patches. I'm not sure how this bug got in,
>> >because in the patch that broke the functionality
>>
On Fri, Jul 29, 2016 at 11:44:53AM +0200, Lukas Slebodnik wrote:
> On (26/07/16 15:00), Jakub Hrozek wrote:
> >Hi,
> >
> >please see the attached patches. I'm not sure how this bug got in,
> >because in the patch that broke the functionality
> >(eef359b508b898ae99d2bf292a43f0f295a2ba5e) I said in
On (26/07/16 15:00), Jakub Hrozek wrote:
>Hi,
>
>please see the attached patches. I'm not sure how this bug got in,
>because in the patch that broke the functionality
>(eef359b508b898ae99d2bf292a43f0f295a2ba5e) I said in the commit message
>that I did the change that is only implemented in the
