We have uuid and global_uuid elements, and we don't use them as IDs. I propose renaming them accordingly, to hash (or hash_local?) and hash_global.
On 04/18/2011 12:45 PM, Denys Vlasenko wrote:
We have uuid and global_uuid elements, and we don't use them as IDs. I propose renaming them accordingly, to hash (or hash_local?) and hash_global.
What do you mean by "we don't use them as IDs"? We use them as local and global crash identifier => global_uuid. Do you think hash_{local,global} is more descriptive?
J.
On Mon, 2011-04-18 at 12:44 +0200, Jiri Moskovcak wrote:
On 04/18/2011 12:45 PM, Denys Vlasenko wrote:
We have uuid and global_uuid elements, and we don't use them as IDs. I propose renaming them accordingly, to hash (or hash_local?) and hash_global.
What do you mean by "we don't use them as IDs"?
We do not use these strings to address the dump directories. We ude directory names for that.
We use them as local and global crash identifier => global_uuid. Do you think hash_{local,global} is more descriptive?
Yes, because in the common usage of these terms, hash is calculated from some data, whereas UUID is just randomly generated.
crash-catcher@lists.fedorahosted.org