Re: erratic behavior commit --allow-empty

Hi Andreas,

as a user, and owner of a repository I do care about the objects that are in it. I do not care about the way they are names, be it numbers or sha's, but for sure about their existence. So, for me it is important if a command creates a new commit or not.

I do not understand this: I have produced several examples that show that it is not created, i.e. that the very same objects are present in the repository after the command execution as they were before it. It is possible, though, that you use the word "create" with a different meaning. Most dictionaries state: "to cause to come into existence", i.e. before creation the thing does not exist, and after creation it does.

-Angelo