Re: erratic behavior commit --allow-empty

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

And you did. The branch happens to point to the same commit as another existing commit, but this is a very common situation. Try this:

# do arbitrary hacking and commit on branch master git checkout -b new-branch gitk

You will see branches "master" and "new-branch" pointing to the same commit (but you HEAD points to new-branch, as "git branch" will tell you).

You still did not describe a _problem_. Up to now, the only "problem" I see is that you have twice the same sha1 showing up, but you did not describe somethine concrete that you wanted to do and did not work.

Right, but the definition of "done" in your sentence includes "reusing an object in the object database".

I just tried this:

rm -fr test git init test cd test date > foo.txt git add . git commit --allow-empty -m foo git checkout --orphan new-branch git commit --allow-empty -m foo

I ended up with a branch "master" and a branch "new-branch", both pointing to the same commit. The new branch _is_ created.

(BTW, --allow-empty is useless here as you have no parent)