<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
On Thursday 02 August 2012 04:30 AM, Gary Martin wrote:<br>
<span style="white-space: pre;">> On 1 Aug 2012, at 20:25, Anish
Mangal <a class="moz-txt-link-rfc2396E" href="mailto:anish@sugarlabs.org"><anish@sugarlabs.org></a> wrote:<br>
><br>
>><br>
> On Friday 20 July 2012 04:05 AM, James Cameron wrote:<br>
> >>> I don't think it should be in a section titled
"Identity", because it<br>
> >>> isn't an identifier, and is only related to
serial number because of<br>
> >>> implementation details.<br>
><br>
> Your probably right. IIRC the idea was to make that
information visible<br>
> alongside the Serial Number.<br>
><br>
> Does it make sense to move it to Software?<br>
><br>
> > I don't have a strong objection to it being in Identity,
but then again, I am not aware of many of the implementation
details of the code behind it – also likely true for most folks
reading it in the field.<br>
><br>
> > If it moves to Software, perhaps it should go below the
Firmware line? James is that more inkeeping with the
implementation? The other option is for a new Lease section below
the Identity section.<br>
><br>
> I don't want to rename the sections because this feature
should only be<br>
> visible when the lease file is actually present.<br>
><br>
> > On this point, the code seems to not behave you describe
above. Testing on an XO-1, the DX3 build 143 International, I see
an item in the Identity section saying "Lease: Not available". The
wording "Not available" suggests something is missing from my XO
when actually this machine does not need a lease, and is
unsecured, this line of information should not be displayed at all
to the user.<br>
></span><br>
<br>
Yes, that is correct. That change will be made when the code is
ported over to mainline.<br>
<br>
<span style="white-space: pre;">> > Regards,<br>
> > --Gary<br>
><br>
><br>
> >>><br>
> >>> I don't wish to constrain your creativity by
saying how to fix that<br>
> >>> though. I'm sure you can imagine many
alternatives.<br>
> >>><br>
><br>
><br>
>><br>
>> _______________________________________________<br>
>> Sugar-devel mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> _______________________________________________<br>
> Sugar-devel mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a></span><br>
<br>
- -- <br>
Anish Mangal<br>
Sugar Labs<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.12 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
<br>
iQEcBAEBAgAGBQJQGdpRAAoJEBoxUdDHDZVpQYIH/11UXRL+4PY23ijV9CoL0Ph6<br>
7vexudcSbOrVNSnPCzFOaKpu9tYxSP8nYmv4S0X8KEGi4PbyAJG5O2vDb67A71SK<br>
TgbGXPqdx6FIa/i+n0axl46DAn21vQLzUQp+wFT9GvgtiBqVJW8iM/T9PlRD8phP<br>
RldsRei0jbA4AdxSHLhjyQypiE7Lcnio6FYAhrW0sYeydVLyXOpCSkv4XyQFcL5t<br>
/liB5bKs1YX9EirFJPJURuKKGWmQ/GC//uk3vmWKV+KaBJwE9koirNU4OvjSwNVX<br>
g51nmt1LwXbmYDtDWgYeUm+5hUPWbjxsFRskgW1Zgedo44XSpYz5r0DVhFzbT6I=<br>
=Xr6U<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>