[Top][All Lists]

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

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

From: Julian T. J. Midgley
Subject: Re: [Gnu-arch-users] "tla commit" generates a patch-set even if there are no changes
Date: Fri, 14 May 2004 10:00:29 +0000 (UTC)

In article <address@hidden>,
Aaron Bentley  <address@hidden> wrote:
>Robert Widhopf-Fenk wrote:
>>>If you want that, you can use the precommit hook to prevent it from 
>>>committing when there are no changes.
>> This is cool, everyday I learn some more nifty tla features ;c)
>> But, still agreeing also to the others, that the default
>> IMHO is not chosen wisely.  tla is strict empty logs,
>> i.e. it will not let me commit if there were no changes in
>> the log.  So I expect it to be strict here too.
>Perhaps you could explain why the defaults are unwise?  What's the harm 
>in an accidental empty commit, aside from a little embarassment?

Conversely, perhaps you could explain the benefits?  So far, I see
none (provided --force is available to allow the commit when it is

Why not go the whole hog and permit people to commit with empty log files?

Julian T. J. Midgley             
Cambridge, England.
PGP: BCC7863F FP: 52D9 1750 5721 7E58 C9E1  A7D5 3027 2F2E BCC7 863F

reply via email to

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