[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patchy email

From: David Kastrup
Subject: Re: Patchy email
Date: Wed, 25 Jan 2012 22:04:52 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux)

David Kastrup <address@hidden> writes:

> Graham Percival <address@hidden> writes:
>> On Wed, Jan 25, 2012 at 09:20:18PM +0100, David Kastrup wrote:
>>> WTF?  That's definitely something in the changes file.  I checked this
>>> and it compiled and I had code that made sure it compiled.  With all the
>>> rebasing to make this fit better I must have displaced the relevant
>>> commit that explicitly makes this compile somehow after all.  I'll be
>>> pushing that ASAP and check the translations afterwards.
>> I see your fix.  However, I'm reluctant to run patchy-staging
>> right now, since it would leave master broken in
>> 1f0a00b69403290b7fc7527b9ab100f95533f954
>> and fixed in
>> 75d0e8cf509685df2e0ed5722803622258673c07
>> True, we're unlikely to have git-bisect stop in between those two
>> commits, but would it be possible for you to include the parser.yy
>> fix in the relevant branch merge so that there isn't any danger
>> when running git-bisect?
> I'll try doing this without messing up again.  15 minutes or so at
> least.

Go ahead.  No diff to last staging regarding the result, but the fix
commit has been pulled into the side branch.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]