From: Jeff King <peff@peff.net>
To: Eli Barzilay <eli@barzilay.org>
Cc: git@vger.kernel.org
Subject: Re: Pushing with --mirror over HTTP?
Date: Mon, 19 Dec 2011 12:12:11 -0500 [thread overview]
Message-ID: <20111219171211.GA20844@sigill.intra.peff.net> (raw)
In-Reply-To: <20072.12104.965815.994761@winooski.ccs.neu.edu>
On Wed, Sep 07, 2011 at 10:58:16PM -0400, Eli Barzilay wrote:
> 5 hours ago, Jeff King wrote:
> > On Mon, Sep 05, 2011 at 12:05:37AM -0400, Eli Barzilay wrote:
> >
> > > Is there anything broken with pushing with mirror over HTTP? I'm
> > > trying that with a github url, and I get a broken-looking error
> > > message:
> > >
> > > remote part of refspec is not a valid name in :.have
> >
> > It's probably nothing to do with http, but rather with alternate
> > object databases on the server (which GitHub uses heavily). The
> > server hands out fake ".have" refs telling you it has some other
> > branch tips to base packs off of. So I suspect the "push --mirror"
> > code is simply wrong for trying to update those refs (it may be
> > exacerbated by using http, though, as the remote helper code seems
> > to have some extra checks).
Sorry for the very delayed response on your bug, but at least I have
good news. :)
It should be fixed by:
http://article.gmane.org/gmane.comp.version-control.git/187373
(I was trying to fix another bug there, but see my followup for a
discussion of .have).
-Peff
prev parent reply other threads:[~2011-12-19 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 4:05 Pushing with --mirror over HTTP? Eli Barzilay
2011-09-07 21:39 ` Jeff King
2011-09-08 2:58 ` Eli Barzilay
2011-12-19 17:12 ` Jeff King [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=20111219171211.GA20844@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=eli@barzilay.org \
--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;
as well as URLs for NNTP newsgroup(s).