On Wed 2015-07-08 15:13:06 -0400, Doug Barton wrote:
> On 7/8/15 12:05 PM, Daniel Kahn Gillmor wrote:
>> On Wed 2015-07-08 14:41:10 -0400, Doug Barton wrote:
>>> I could see the git Id useful for both releases and dailies. For dailies
>>> however if I want to know "On what date was this built?" I'd rather see
>>> the date than have to cross-reference it with a commit Id.
>>
>> but why do you want to know "on what date was this built?"
>
> There are any number of answers to that question ...
can you give some other examples?
> it's not clear to me why you're resistant to the idea of putting the
> build date in the dailies.
because it answers no useful questions i've heard of; it makes it
difficult to reproduce the build deterministically; and it is actively
misleading if there are no changes between two days. (i'm on build
2015-05-04; should i install build 2015-05-06? are there any changes?
i can't tell)
>> -- is it so
>> you can decide which of two versions to run (you want the more recent
>> one)? or because you want to know what code went into it?
>>
>> if it's just "i want the more recent one" then a git commit id coupled
>> with a commit count from the last tag would be another approach (this is
>> how gnupg betas are counted -- beta414 would be built from the 414th
>> commit since the last official version.
>
> Even assuming that "I want the more recent one" is the answer, your
> method still requires a cross-reference to git. I'm simply suggesting
> that the date be available directly instead.
there's no need to cross-reference to git at all. 1.9.0~prerelease
nightly (build 353) has 4 changes more than 1.9.0~prerelease nightly
(build 349).
--dkg
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
