Re: erratic behavior commit --allow-empty

Angelo Borsotti <angelo.borsotti@gmail.com> writes:

This is fundamentally how Git works. You probably didn't notice it, but if you do

echo 'some content' > file1.txt git add file1.txt git commit -m "file1"

echo 'some content' > file2.txt git add file2.txt git commit -m "file2"

Then the second commit does not "create" a new blob object for file2.txt, because it has the same content as an existing one. But the point is: you really don't care, or indeed, you care about sharing the blob objects to save disk space.

It is predictible: give it twice the same inputs in the same conditions, and it will yield the same output.

You still didn't tell us where the problem was. You are unhappy with having twice the same sha1 for the same object, but what concrete bad consequence does this have? (except for saving bandwidth in addition to disk space when trying to push your commit)