On 17.06.2014 07:39, Ben Skeggs wrote:
[snip]
In any case, I encountered the oops myself earlier (absolutely nothing
to do with that commit) and fixed it here. I've sent it onto Dave for
the next -fixes merge, so hopefully it'll help your case too.
Has this anything to do with
"Machine
On 17.06.2014 07:39, Ben Skeggs wrote:
[snip]
In any case, I encountered the oops myself earlier (absolutely nothing
to do with that commit) and fixed it here. I've sent it onto Dave for
the next -fixes merge, so hopefully it'll help your case too.
Has this anything to do with
Hello Ben,
> > 8777c5c11764d8336d8270f96778158c34c92108 (which is mentioned as the
> > first bad commit above...) is a tiny commit, so I have no idea what
> > you mean by "too large for your taste".
for example I would not export a symbol and do something else in the
same commit, but would split
On Tue, Jun 17, 2014 at 3:39 PM, Ben Skeggs wrote:
> On Tue, Jun 17, 2014 at 3:33 PM, Thomas Glanzmann wrote:
>> Hello Ben,
>>
>>> Are you able to double-check that bisect? I'm not at all sure how
>>> that particular commit could trigger the issue you're seeing. Some of
>>> the others,
On Tue, Jun 17, 2014 at 3:33 PM, Thomas Glanzmann wrote:
> Hello Ben,
>
>> Are you able to double-check that bisect? I'm not at all sure how
>> that particular commit could trigger the issue you're seeing. Some of
>> the others, certainly. It might be worth trying a couple of times
>> before
Hello Ben,
> Are you able to double-check that bisect? I'm not at all sure how
> that particular commit could trigger the issue you're seeing. Some of
> the others, certainly. It might be worth trying a couple of times
> before marking something as "good", in case there's a timing aspect to
>
Hello Ben,
Are you able to double-check that bisect? I'm not at all sure how
that particular commit could trigger the issue you're seeing. Some of
the others, certainly. It might be worth trying a couple of times
before marking something as good, in case there's a timing aspect to
the
On Tue, Jun 17, 2014 at 3:33 PM, Thomas Glanzmann tho...@glanzmann.de wrote:
Hello Ben,
Are you able to double-check that bisect? I'm not at all sure how
that particular commit could trigger the issue you're seeing. Some of
the others, certainly. It might be worth trying a couple of times
On Tue, Jun 17, 2014 at 3:39 PM, Ben Skeggs skeg...@gmail.com wrote:
On Tue, Jun 17, 2014 at 3:33 PM, Thomas Glanzmann tho...@glanzmann.de wrote:
Hello Ben,
Are you able to double-check that bisect? I'm not at all sure how
that particular commit could trigger the issue you're seeing. Some
Hello Ben,
8777c5c11764d8336d8270f96778158c34c92108 (which is mentioned as the
first bad commit above...) is a tiny commit, so I have no idea what
you mean by too large for your taste.
for example I would not export a symbol and do something else in the
same commit, but would split them up
On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann wrote:
> Hello Ben,
> commit
Hey Thomas,
Are you able to double-check that bisect? I'm not at all sure how
that particular commit could trigger the issue you're seeing. Some of
the others, certainly. It might be worth trying a couple of times
On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann tho...@glanzmann.de wrote:
Hello Ben,
commit
Hey Thomas,
Are you able to double-check that bisect? I'm not at all sure how
that particular commit could trigger the issue you're seeing. Some of
the others, certainly. It might be worth trying a
12 matches
Mail list logo
