Re: Git's database structure

From: Mike Hommey <mh@glandium.org>
Date: Sep 4, 2007, 16:07 UTC
Message-ID: <20070904160726.GA17509@glandium.org>
In-Reply-To: <46DD7FE4.1060908@op5.se>

On Tue, Sep 04, 2007 at 05:55:16PM +0200, Andreas Ericsson <ae@op5.se> wrote:

Show 5 quoted lines

> Each root tree can only ever belong to a single commit, unless you
> intentionally force git to make completely empty commits. git
> won't complain about this, so long as you don't make two in the
> same second, because it relies more heavily on the DAG than on
> developer sanity.

Actually, you don't need to be insane to have multiple commits pointing
at the same root tree. It is actually very easy:
- git clone
- do some stuff on your master branch and commit
- send your changes upstream
- upstream applies as is
- git pull

You now have everything merged, and the last commit on your master branch, while being a different commit object due to its parenting, has the same root tree as the tip of the remote branch.

Mike