[Top][All Lists]

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

Re: Removing 'scriptversion' from our scripts

From: Stefano Lattarini
Subject: Re: Removing 'scriptversion' from our scripts
Date: Wed, 07 Mar 2012 08:35:39 +0100

On 03/06/2012 10:06 PM, Peter Rosin wrote:
> Stefano Lattarini skrev 2012-03-06 21:58:
>> [re-adding the list]
>> On 03/06/2012 09:18 PM, Peter Rosin wrote:
>>>> You also forgot scriptversion...
>> True, but see below.
>>> ...which is the reason this change should have been committed on msvc.
>>> Updating compile/depcomp/ar-lib on maint destroys the rule saying
>>> "newer is better".
>> But that's a lie anyway when we use multiple branches, as the present
>> situation shows once again.  OK, enough is enough.  Tomorrow I'll just
>> nuke all the 'scriptversion' lines from our scripts (in maint and master
>> as well).
> It wouldn't have been a lie if changes happened in the right place,
> at least not for the vast majority of changes, i.e. the backwards
> compatible ones.  Also remember that the consensus seemed to be that
> scriptversion is useful last time this came up.
But that last discussion revolved mostly around issues with spurious merge
conflicts due to diverging 'scriptversion' lines, which is easily solved
anyway (just use the date of when you're doing the merge) and is a red
herring w.r.t. the real problem -- that is, for "orthogonal" branches,
there is no "newest" version of a script.  If we wanted to be honest in
declaring the version, we should have a git hook or something similar
that substitutes the SHA1 and date of the last commit (as reachable from
the current HEAD) that modified the given script.  Not sure how this can
be done, or how difficult it would be to do so.


reply via email to

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