From: "Carlos Martín Nieto" <cmn@elego.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: vra5107 <venkatram.akkineni@gmail.com>, git@vger.kernel.org
Subject: Re: Can a git changeset be created with no parent
Date: Mon, 26 Sep 2011 23:41:39 +0200 [thread overview]
Message-ID: <1317073309.5579.9.camel@centaur.lab.cmartin.tk> (raw)
In-Reply-To: <7vaa9r2jii.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-09-26 21:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 14:15 Can a git changeset be created with no parent vra5107
2011-09-25 14:33 ` Andreas Ericsson
2011-09-25 14:33 ` Carlos Martín Nieto
2011-09-26 19:25 ` Junio C Hamano
2011-09-26 21:41 ` Carlos Martín Nieto [this message]
2011-09-27 14:43 ` [PATCH] Docs: git checkout --orphan: `root commit' and `branch head' Michael Witten
2011-09-27 15:02 ` Matthieu Moy
2011-09-27 15:46 ` [PATCH v2] " Michael Witten
2011-09-27 16:01 ` Matthieu Moy
2011-09-27 16:13 ` Michael Witten
2011-09-27 16:53 ` Matthieu Moy
2011-09-27 17:09 ` Michael Witten
2011-09-27 20:59 ` Philip Oakley
2011-09-28 16:23 ` [PATCH v3] " Michael Witten
2011-09-28 20:34 ` Junio C Hamano
2011-09-29 15:52 ` Michael Witten
2011-09-29 15:44 ` [PATCH v4] Docs: git checkout --orphan: Copyedit, and s/root commit/orphan branch/ Michael Witten
2011-09-29 16:44 ` Michael Witten
2011-09-29 20:05 ` Philip Oakley
2011-09-29 18:11 ` In favor of "git commit --no-parent" Junio C Hamano
2011-09-29 18:52 ` Michael Witten
2011-09-29 18:59 ` [PATCH] Documentation/git-checkout.txt: Explain --orphan without introducing an undefined "orphan branch" Junio C Hamano
2011-09-29 19:02 ` Michael Witten
2011-09-29 21:02 ` In favor of "git commit --no-parent" Phil Hord
2011-09-29 21:28 ` Michael Witten
2011-09-29 21:50 ` Phil Hord
2011-09-29 22:01 ` Michael Witten
[not found] ` <CABURp0q8YhTS-GDYOANEa19P-V2wf_EUTo=RHqnhDB619w=y-w@mail.gmail.com>
[not found] ` <7vd3ejrqin.fsf@alter.siamese.dyndns.org>
2011-09-29 21:54 ` Junio C Hamano
2011-09-29 22:07 ` Phil Hord
2011-09-29 22:29 ` Michael Witten
2011-09-29 22:32 ` Michael Witten
2011-09-29 23:08 ` Junio C Hamano
2011-09-30 0:51 ` Michael Witten
2011-09-30 2:28 ` Junio C Hamano
2011-09-29 22:07 ` Michael Witten
2011-09-27 15:49 ` [PATCH] Docs: git checkout --orphan: `root commit' and `branch head' Michael J Gruber
2011-09-27 16:02 ` Michael Witten
2011-09-27 17:25 ` Junio C Hamano
2011-09-27 17:50 ` Michael Witten
2011-09-27 20:34 ` Eric Raible
2011-09-27 21:31 ` Philip Oakley
2011-09-27 21:42 ` Jeff King
2011-09-27 23:28 ` Michael Witten
2011-09-27 23:35 ` Jeff King
2011-09-27 23:44 ` Michael Witten
2011-09-28 0:32 ` Junio C Hamano
2011-09-28 13:40 ` Michael Witten
2011-09-28 13:45 ` Matthieu Moy
2011-09-28 13:50 ` Michael Witten
2011-09-28 14:09 ` Matthieu Moy
2011-09-28 14:35 ` Michael Witten
2011-09-28 14:45 ` Matthieu Moy
2011-09-28 15:06 ` Michael Witten
2011-09-28 18:17 ` Junio C Hamano
2011-09-28 4:04 ` Jay Soffian
2011-09-28 4:37 ` Michael Witten
2011-09-28 8:00 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1317073309.5579.9.camel@centaur.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=venkatram.akkineni@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).