Re: Make commit messages optional

>> And I still don't get why the --allow-empty-message is not
>> sufficient to meet your use case. git supports what is being
>> requested already, not that it is allowed where I am. Are we
>> talking about setting --allow-empty-message as the default? That is
>> a major behavioural change. You could create a git command alias to
>> always specify this option. So what is the point of this?
>>
>
> My proposal is that it absolutely is enough, functionally - but the
> abundance of "we should change something" concerns in this thread and
> elsewhere suggest, to me, that it might not be sufficiently
> discoverable; hence the "advice" proposal.