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

[Tom Lord]

    > From: Jani Monoses <address@hidden>

    > > Perhaps you could explain why the defaults are unwise?  What's the harm 
    > > in an accidental empty commit, aside from a little embarassment?

    > confusion of new users and mails to gau resulting in wasted time overall. 
I
    > thought it was a bug too and wrote to the list a couple month ago. From 
the
    > answers I understood there are valid situations when you would use this 
but
    > they are less frequent as accidental empty commits. I think Tom said that
    > larch had a force flag and that he wouldn't mind one for tla
    > either.

I may have but I've changed my mind.


    > I agree with others in the thread that the current default surprises.

I think there are two sources of unintended commits.

One source is commiting from the wrong directory.  I find this easy to
do when I have many emacs windows open (each window has its own $CWD)
and I use the wrong one by mistake.  My last mail in this thread,
opening a bug, proposed a solution to this problem.


The other source is committing twice in a row.   Someone mentioned
that they do that.   I guess you commit using the -L flag so you don't
have to edit a log file.   Then get distracted for a second.   Then
issue that same command again.   I'm not sure anything can or should
be done about his kind of mistake.   People should improve their
focus, instead :-)

-t