From: Carlos Martín Nieto <cmn@elego.de>
Date: Mon, 26 Sep 2011 21:41:39 GMT
Subject: Re: Can a git changeset be created with no parent
Message-ID: <1317073309.5579.9.camel@centaur.lab.cmartin.tk>
In-Reply-To: <7vaa9r2jii.fsf@alter.siamese.dyndns.org>

On Mon, 2011-09-26 at 12:25 -0700, Junio C Hamano wrote:
> Carlos Martín Nieto <cmn@elego.de> writes:
> 
> > On Sun, 2011-09-25 at 07:15 -0700, vra5107 wrote:
> >> Hi
> >> 
> >>         I am currently in the process of converting a large hg repository.
> >> One of the changesets has no parents assigned. So to mirror that is it
> >> possible to create a git changeset that doesnot have a parent ?
> >
> > They're called commits in git, and yes it's possible. They are called
> > orphan commits and it's what you get when you do the first commit in the
> 
> Just to set the terminology straight, s/orphan/root/;

Ah, quite.

> 
> > repository.
> >
> > You can do this with 'git checkout --orphan somebranch'. Notice that the
> 
> The orphan here refers to the fact that the next commit will not be a
> child of the current commit. The resulting one is a "root" commit.

The manpage mentions that an orphan branch is created. I guess that's
where I got my "orphan commit" name.