All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"Ákos, Tajti\"" <akos.tajti@intland.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: 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 15:01:11 +0200	[thread overview]
Message-ID: <51A5FC17.8000608@intland.com> (raw)
In-Reply-To: <CALkWK0m=m89QcnMNg9gEVeb7ZHSRd7ZMcL+y8gYuzn8YCTsSYw@mail.gmail.com>

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?

Thanks,
Ákos

2013.05.29. 14:54 keltezéssel, Ramkumar Ramachandra írta:
> Matthieu Moy wrote:
>>> the manual of git init says: "An initial HEAD file that references the
>>> HEAD of the master branch is also created."
>>>
>>> However, after creating the repository using git init there's no
>>> master branch.
>> Right, but HEAD still points to it ;-). We sometimes call this an
>> "unborn branch".
> Right.  Let me also add that our prompt has support for this; on an
> unborn branch, my prompt looks like:
>
> artagnon|master#:/tmp/foo$
>                 ^
> 	       the # indicates unborn branch
>
> Please consider using contrib/completion/git-prompt.sh to make your life easier.

  reply	other threads:[~2013-05-29 13:01 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" [this message]
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

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=51A5FC17.8000608@intland.com \
    --to=akos.tajti@intland.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.