Re: erratic behavior commit --allow-empty
- From
- Angelo Borsotti <angelo.borsotti@gmail.com>
- Date
- Oct 3, 2012, 11:37 UTC
- Message-ID
- <CAB9Jk9Dqoom-hBQPG5iqe2JyiJtVoFWZ9-5W9ktUsa9F9mbXRQ@mail.gmail.com>
- In-Reply-To
- <m2fw5vooem.fsf@linux-m68k.org>
Hi Andreas,
> > Where does the manual say that --allow-empty implies a different and > unique commit? >
In the git commit man page:
"--allow-empty
Usually recording a commit that has the exact same tree as its sole parent commit is a mistake, and the command prevents you from making such a commit. This option bypasses the safety, and is primarily for use by foreign SCM interface scripts."
By reading: "the command prevents" I understand that a new commit is not created, and "This option bypasses" that it is instead created.
Perhaps my reading was a bit straightforward, but a man page is not a sort of ancient holy writing that the reader has to sift every word to understand hidden meanings, it should be something clear and plain.
-Angelo