Re: [PATCH] Add option to git-commit to allow empty log messages

Sverre Rabbelier [off-list ref] writes:

On Sun, Apr 4, 2010 at 21:11, Junio C Hamano [off-list ref] wrote:

quoted

As a Porcelain, "git commit" has some leeway to enforce sensible policy on
the users, and "forbid commit that does not explain anything" is one such
policy.  It is not generally a good idea to expose the full capabilities
of plumbing to Porcelain if it leads to bad user behaviour, and such
"artificial" limitations are safety features we do not want to remove.

You contradict yourself:

I personally don't mind very much removing --allow-empty, though.

Heya,

On Sun, Apr 4, 2010 at 22:57, Junio C Hamano [off-list ref] wrote:

Sverre Rabbelier [off-list ref] writes:

quoted

You contradict yourself:

I personally don't mind very much removing --allow-empty, though.

Ah, hmm. I vaguely remember some discussion in the past about empty
commits, but I'm not sure what the conclusion there was? I think it
was something like "if you want to create a marker, use tags instead,
there's really no reason to be using --allow-empty". Wasn't there some
use case for "--allow-emtpy" when creating an unrooted branch with an
empty starting point, or somesuch?

-- 
Cheers,

Sverre Rabbelier