From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: Wolfgang Denk <wd@denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Takahiro Akashi <takahiro.akashi@linaro.org>
Subject: Re: [BUG] Cloning with git HEAD fails for some repositories
Date: Fri, 22 Mar 2019 16:50:34 +0000 [thread overview]
Message-ID: <20190322165034.GA23124@dcvr> (raw)
In-Reply-To: <20190322093132.GA17498@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> On Fri, Mar 22, 2019 at 09:21:14AM +0100, Wolfgang Denk wrote:
>
> > Dear Jeff,
> >
> > In message <20190322071231.GA26114@sigill.intra.peff.net> you wrote:
> > >
> > > However, so does the parent of 17966c0a63d. So I don't know if the
> > > u-boot-efi repo is just broken, or if there's some other different bug
> > > at play.
> >
> > git fsck reports a number of dangling tags, but no other issues:
>
> Weird. I had set http.maxrequests to "1" to give more readable output
> from GIT_CURL_VERBOSE, etc. It fails with that setting, but not with the
> default of 5. Which certainly seems like a bug, but one that has been
> there for a while (at least since v2.9.x, which I tested).
I couldn't reproduce an error after porting your patch to
master (commit 041f5ea1cf987a40 "The third batch"):
https://80x24.org/spew/20190322163449.25362-1-e@80x24.org/raw
So you might've hit an ephemeral error (bad connection,
HTTP server restarting, etc).
GIT_CURL_VERBOSE=1 git \
-c http.maxRequests=1 -c http.followRedirects=true clone \
http://git.denx.de/u-boot-efi.git
next prev parent reply other threads:[~2019-03-22 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7e4a2f1d-2b3a-eb83-d3f1-9ac63d68991b@gmx.de>
[not found] ` <20190322005107.GL9937@linaro.org>
2019-03-22 6:02 ` [BUG] Cloning with git HEAD fails for some repositories Heinrich Schuchardt
2019-03-22 7:12 ` Jeff King
2019-03-22 8:21 ` Wolfgang Denk
2019-03-22 9:31 ` Jeff King
2019-03-22 16:50 ` Eric Wong [this message]
2019-03-22 17:42 ` Heinrich Schuchardt
2019-03-22 18:09 ` Eric Wong
2019-03-22 18:41 ` Heinrich Schuchardt
2019-03-22 20:35 ` Eric Wong
2019-03-23 8:53 ` Jeff King
2019-03-24 12:07 ` [PATCH 0/3] fix dumb-http fetch with alternates Jeff King
2019-03-24 12:08 ` [PATCH 1/3] http: factor out curl result code normalization Jeff King
2019-03-24 12:09 ` [PATCH 2/3] http: normalize curl results for dumb loose and alternates fetches Jeff King
2019-03-24 12:13 ` [PATCH 3/3] http: use normalize_curl_result() instead of manual conversion Jeff King
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=20190322165034.GA23124@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=takahiro.akashi@linaro.org \
--cc=wd@denx.de \
--cc=xypron.glpk@gmx.de \
/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.