lmi
[Top][All Lists]
Advanced

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

Re: [lmi] Building wx from trunk


From: Greg Chicares
Subject: Re: [lmi] Building wx from trunk
Date: Fri, 09 Jan 2015 22:18:29 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0

On 01/05/2015 12:31 AM, Greg Chicares wrote:
> On 12/06/2014 11:04 AM, Greg Chicares wrote:
>> On 2014-11-21 18:33Z, Greg Chicares wrote:
>>> On 2014-11-05 15:54Z, Greg Chicares wrote:
>>>> On 2014-10-25 00:39Z, Greg Chicares wrote:
>>>>> 
>>>>> [...] so that we're all using the same tarball on this shore
>>>>> (set your secret decoder ring to the latest recommended SHA1, today's 
>>>>> being
>>>>>   e89736135431a54bb6d7c64001c608a42d4dad4a
>>>>> ):
>>>> 
>>>> Update--please set your secret decoder ring to:
>>>>   06ddf44a276524d9e154cbe6c7dd4f3d8442f912
>>>> Your new tarball should have this md5sum:
>>>>   7a68e44db3eddf5520595a5e21128d7a
>>> 
>>> Update--please set your secret decoder ring to:
>>>   1a4e398732e84c8d1b0c0baf92b1ec9b3e9ba60e
>>> Your new tarball should have this md5sum:
>>>   ddd10933ff8d1a56eb34039e98c3932e
>> 
>> Update--please set your secret decoder ring to:
>>   8ae9dae3b4ae4f1ddeef409d51066263d799e0e2
>> Your new tarball should have this md5sum:
>>   9fc98d1412476f0b8ee8f9fd5a31d263
> 
> Update--please set your secret decoder ring to:
>   6022671ee5bd0f718cf0ad9ff2aefd2d1f154c58
> Your new tarball should have this md5sum:
>   f6612e80cd732a370bbde5a529808290

Update--please set your secret decoder ring to:
  510ae4e0b44f78ec76f474c61290aadd1a8313e0
Your new tarball should have this md5sum:
  985edf1d1e7020c483fa1079cd25fafa
Use this with lmi revision 6084, committed 20150109T2213Z.

With the last snapshot, editing a census field with the pop-up
input-sequence editor dialog caused the field to retain an
"open" appearance, as though editing wasn't quite complete;
and many such fields could simultaneously be left in that
state. This update, with lmi revision 6084, addresses that
problem. Cf.:
  
https://github.com/wxWidgets/wxWidgets/commit/510ae4e0b44f78ec76f474c61290aadd1a8313e0

(In the past, we've used whatever SHA was most recent when we
happened to need an update. Today's SHA corresponds to the
most recent update that we know we need. This should be a
little safer, because we can't be harmed by any defective
commit that comes after the one we want.)




reply via email to

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