Subject: Re: erratic behavior commit --allow-empty

From: Tomas Carnecky <[email-masked]>
Date: Wed, 03 Oct 2012 12:25:46 +0000

On Wed, 03 Oct 2012 10:24:00 +0200, Angelo Borsotti <[email-masked]> wrote:
> create a new one. To force it to create a brand new one I added
> --allow-empty to it
> because the man page stated that it would bypass the check that prevents to make
> a new one. The I discovered that sometimes --allow-empty does not behave as
> expected.

The documentation only states that it will skip the 'same tree as parent'
check, not that it will *always* create a new commit.