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

[William Dode]

Miles Bader <address@hidden> writes:

> On Thu, May 13, 2004 at 02:51:52PM -0400, James Blackwell wrote:
>> > IMHO it should complain that there are no changes and
>> > exit(-1), what it it good for generating an empty
>> > patch-set.  (o.k. there is a log in the patch-set but
>> > nothing else ;-/)
>> 
>> Not so. :) 
>> Here's two reasons: 
>
> Those are easily handled with an option to force a commit even when there
> are no changes (ala CVS), e.g., --force.
>
> I agree with the original poster, commit should by default err on the side of
> not committing (in general!).

I'm agree also, i often commit two times for nothing... And after i
want to remove the last one and it's the begin of the dark side ! remove
the history !

-- 
William Dodé - http://flibuste.net