From: Junio C Hamano <gitster@pobox.com>
To: Samuel Williams <space.ship.traveller@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: Trying to push into empty repo, get fatal: bad revision 'HEAD'
Date: Tue, 31 Mar 2015 17:00:59 -0700 [thread overview]
Message-ID: <xmqqego4ogxw.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAHkN8V8cpZUmCi6=MUcsCOCBe6H_G6btr6WaV2vVrO1Nm_r4tg@mail.gmail.com> (Samuel Williams's message of "Wed, 1 Apr 2015 12:29:20 +1300")
Samuel Williams <space.ship.traveller@gmail.com> writes:
> I would expect if you push to an empty repo, it would update it
> (because denyCurrentBranch = updateInstead).
Good finding.
I think the current implementation of updateInstead is set up to
bootstrap from an empty repository but only supports incremental
updates once the receiving repository and its working tree gets set
up. But I do not think it was a conscious design decison to forbid
bootstrapping an empty repository, but was a mere gap in the
implementation. At least, I do not think of a reason why we should
forbid it (and I am Cc'ing Dscho to confirm).
Fixing it should not be too hard, but I am on a bus right now so...
next prev parent reply other threads:[~2015-04-01 0:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 23:29 Trying to push into empty repo, get fatal: bad revision 'HEAD' Samuel Williams
2015-04-01 0:00 ` Junio C Hamano [this message]
2015-04-01 1:36 ` Junio C Hamano
2015-04-01 6:15 ` Junio C Hamano
2015-04-01 8:51 ` Johannes Schindelin
2015-04-01 18:00 ` Junio C Hamano
2015-04-02 5:07 ` Johannes Schindelin
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=xmqqego4ogxw.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=space.ship.traveller@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 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.