From: Junio C Hamano <gitster@pobox.com>
To: "Ákos, Tajti" <akos.tajti@intland.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
git@vger.kernel.org
Subject: Re: git init doesn't create master branch
Date: Wed, 29 May 2013 11:37:28 -0700 [thread overview]
Message-ID: <7va9ndtyxj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <51A5FC17.8000608@intland.com> ("Ákos, Tajti"'s message of "Wed, 29 May 2013 15:01:11 +0200")
"Ákos, Tajti" <akos.tajti@intland.com> writes:
> Thanks for clarifying this thing for me! I don't really insist on
> having a master branch it's just that I tried to pull from a
> repository bundle and I got this error message:
>
> "Cannot merge multiple branches into empty head"
>
> The command was:
>
> git pull ../dump.dmp refs/heads/*:refs/heads/*
>
> Is this a better way of doing this?
You are not trying to merge all branches contained in the dump, so
"pull" is a wrong thing to use here.
$ git fetch --update-head-ok ../dump.dmp refs/heads/*:refs/heads/*
would be one way. Or you could just use the dumpfile as if it were
a normal remote and say (without running "git init")
$ git clone dump.dmp undump
to extract it in a new directory "undump" (this may require your
dumpfile created with HEAD, though).
prev parent reply other threads:[~2013-05-29 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 12:47 git init doesn't create master branch "Ákos, Tajti"
2013-05-29 12:50 ` Matthieu Moy
2013-05-29 12:54 ` Ramkumar Ramachandra
2013-05-29 13:01 ` "Ákos, Tajti"
2013-05-29 13:08 ` Matthieu Moy
2013-05-29 13:20 ` "Ákos, Tajti"
2013-05-29 13:20 ` Ramkumar Ramachandra
2013-05-29 18:37 ` Junio C Hamano [this message]
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=7va9ndtyxj.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=akos.tajti@intland.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
/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