Re: erratic behavior commit --allow-empty
- From
- Tomas Carnecky <tomas.carnecky@gmail.com>
- Date
- Oct 3, 2012, 12:25 UTC
- Message-ID
- <1349267146-ner-5314@calvin>
- In-Reply-To
- <CAB9Jk9DFb2s4s00yCNUytxFdrOQKPEKZGsXpKzwZDo5WAOdXaQ@mail.gmail.com>
On Wed, 03 Oct 2012 10:24:00 +0200, Angelo Borsotti <angelo.borsotti@gmail.com> wrote:
Show 5 quoted lines
> 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.