Re: erratic behavior commit --allow-empty
- From
- Angelo Borsotti <angelo.borsotti@gmail.com>
- Date
- Oct 3, 2012, 13:08 UTC
- Message-ID
- <CAB9Jk9Au32hGf-UB2PRa46qaA6GtpJ3jWL=SWWXns=Jc6O97KQ@mail.gmail.com>
- In-Reply-To
- <1349267146-ner-5314@calvin>
Hi Thomas,
> The documentation only states that it will skip the 'same tree as parent' > check, not that it will *always* create a new commit.
Ok, understood: you believe that the documentation is clear, and I that it is somehow not. I would prefer to have it more plain.
But that is not all the story. The behavior of the command remains time-dependent, so that a user cannot reliably predict its result. I think that this is an ill-specified option. I would not insist in removing it (although that would be the correct solution), but at least to warn the user about this possibly unexpected behavior.
-Angelo