Re: [Monotone-devel] Merging branch to allow duplicate key names, have certs use key hash

[Thomas Keller]

Timothy Brownawell schrieb:
>>> 'automate certs' prints the key hash where it printed the key name
>>> before, and 'automate keys' lists both local and given names instead of
>>> only one name.
>> I've checked 'automate certs' output and saw that only for new revisions
>> the key hash is outputted
>>
>>       key [1aaecf3a7c227e5545b0504aea5d3716d3128117]
>> signature "ok"
>>      name "author"
>>     value "address@hidden"
>>     trust "trusted"
>>
>> while for old revisions key still points to the plain key name
>>
>>       key "address@hidden"
>> signature "ok"
>>      name "author"
>>     value "Timothy Brownawell  <address@hidden>"
>>     trust "trusted"
>>
>> Do you think its a good idea to mix both output types together?
> 
> Strange. It doesn't look like it should be able to print the key name
> like that.

Woops, sorry, entirely my fault. You're right, I managed somehow to look
at the old output. Of course it displays the key's hash for all, old and
new certs.

Sorry again,
Thomas.


-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc
Description: OpenPGP digital signature