git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Nipunn Koorapati <nipunn1313@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: Partial clone fails with file:/// URI
Date: Wed, 14 Oct 2020 13:27:46 -0400	[thread overview]
Message-ID: <20201014172746.GB2044338@nand.local> (raw)
In-Reply-To: <CAN8Z4-XGbb_z3vmJYATONmBkxBcfxwyC-_4XEOkP0sxsdT9wxw@mail.gmail.com>

On Wed, Oct 14, 2020 at 06:04:18PM +0100, Nipunn Koorapati wrote:
> Hi,
>
> I've been building git from source and directly using the executable. Roughly
> ```
> cd git
> make
> cd ..
> git/git clone --filter=blob:none file://$(pwd)/git a_clone_of_git
> ```
>
> This is what I was missing:
> git config uploadpack.allowanysha1inwant true
>
> If this is not set, then the checkout fails w/ a
>
> fatal: protocol error: bad pack header
>
> Perhaps the error message and/or docs could be improved here to
> something with more detail than "bad pack header"?
> Not seeing anything to suggest this in the docs
> https://git-scm.com/docs/partial-clone

Ah. OK; I feel much better knowing what the difference between our two
setups is. This is a long-standing issue (I remember seeing it when I
was experimenting with partial clones several releases ago) so I'm glad
that we _don't_ have to treat this as a regression in 2.29.

> Thanks for the prompt response. Appreciated!
> --Nipunn

Thanks,
Taylor

  reply	other threads:[~2020-10-14 17:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 16:38 Partial clone fails with file:/// URI Nipunn Koorapati
2020-10-14 16:56 ` Taylor Blau
2020-10-14 17:04   ` Nipunn Koorapati
2020-10-14 17:27     ` Taylor Blau [this message]
2020-10-14 23:41       ` Nipunn Koorapati
2020-10-15  1:20     ` 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=20201014172746.GB2044338@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=nipunn1313@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 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).