Re: erratic behavior commit --allow-empty
- From
- Angelo Borsotti <angelo.borsotti@gmail.com>
- Date
- Oct 3, 2012, 17:37 UTC
- Message-ID
- <CAB9Jk9Aa4d4H5q1euCJ4hdc_K9iBrfiJFnyAYQ+BRNX3D023gg@mail.gmail.com>
- In-Reply-To
- <m2fw5va4jc.fsf@igel.home>
Hi Andreas,
> But the commit object _is_ created, it just doesn't have a unique name.
The command may internally create the commit object, compute its sha and then seeing that there is already one in the repo with the same sha, throw it away. But this is an implementation detail. The net result for the user is that after the command there are no new objects.
-Angelo