Re: [Gnu-arch-users] "tla commit" generates a patch-set even if there are no changes

[Wazow]

Aaron Bentley <address@hidden> writes:

> I said "the harm comes from changing the default behavior".  That's a
> script-unfriendly policy.
>
>> Your existing scripts would merely need to be changed to use the option.
>
> Yes.  In general, that's bad.

It has always been an advantage of free software projects that they are
legacy free (contrary to many commercial projects). Some free software
project took this compatibility breaking to the extreme (gcc and glibc
among the greatest). It is nearly always the right thing to introduce
such a small inconsistency for the sake of better next release. If
people really hate it then this could be made optional (whether --force
is default or not).

> People should be able to update to the latest version of tla without
> breaking their existing tools.  I've found out just recently that I've
> been distributing an obsolete script, because tla shifted underneath
> me. I shouldn't have to test every script in my collection every time
> I do a tla update. 

You should. In fact at least if you ship your scripts to the public you
should have a solid bunch of tests which you run before each release.

Andrzej