Re: [Monotone-devel] empty commit / question from Datakko

[Adam Logghe]

I agree that "empty commits" should be possible but it should be an
error by default.

Most of the time an empty commit for me would be a screwup in the form
of "hmm forgot to write out my buffer". I definetly want to be
warned/stopped. I would ask for both a "force" and "did you mean to make
an empty commit? y/n".

"force" as the only way to commit anyway is not good in that "force" can
be very tricky in command lines. You have to start getting specific as
to which check you want to "force" your way over on commit. This leads
to an explosion of "force" specifiers which leads to "I can't remember
the right command". If I have "y/n" then I don't have to remember.

Adam

Nathan Myers wrote:
> On Mon, May 24, 2004 at 02:34:33PM +0200, Nico Schottelius wrote:
>
>>In IRC Datakko asked about empty commits from monotone. Right said that
>>I read the thread on tla asking more or less the same.
>>The tla guys decided empty commits explicit to be allowed and I think
>>it's quite senseful. Read more at bottom.
>
>
> It should be possible to do an empty commit, but it should be reported
> as an error by default, because, while it may be a sensible thing to
> do, it's more likely to be pilot error, e.g. committing in the wrong
> directory.  The error message should say how to force it if that was
> what you really meant to do.  The option to force it should be safe to
> use all the time (i.e. not force anything else) so it can be used in
> scripts.
>
> Nathan Myers
> address@hidden
>
>
> _______________________________________________
> Monotone-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/monotone-devel