From: Fraser Hanson <fraser.hanson@gmail.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org
Subject: Re: git fetch recursion problem
Date: Thu, 1 Jun 2023 15:57:39 -0700 [thread overview]
Message-ID: <CA+3o5aNgChKi-m6F_sYr4Sc+VXP-K2BCMpTpY8Km+kH5u9tkCQ@mail.gmail.com> (raw)
In-Reply-To: <kl6lzg5iztzw.fsf@chooglen-macbookpro.roam.corp.google.com>
Thanks for the theory!
This repo has no .gitmodules file.
I tried running `git fetch --no-recurse-submodules` in one of my
broken repos, but it does not prevent the bug from happening.
I also tried removing the submodule configuration in .git/config, that
had no effect either.
Maybe something is unusual on the server side. I've set up my own git
server attempting to reproduce similar apache and git versions as on
our corporate mirror but so far cannot reproduce the bug.
I've compared the GIT_CURL_VERBOSE output to what I get for the same
repo from github, but it's not very helpful.
Github uses HTTP2 and my git client sends different service api calls
to github so there's not much basis for comparison here.
My main theory was that maybe the server-side git version was too old
to handle partial clones properly.
Partial clones were introduced in git 2.25. On my test git server, I
set the server-side git version to 2.7.2.
This did not reproduce the bug -- on the client side using a recent
git version, I was still able to pull partial clones and then fetch
from origin after my local copy went out of date.
next prev parent reply other threads:[~2023-06-01 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 17:57 git fetch recursion problem Fraser Hanson
2023-05-30 19:11 ` Fraser Hanson
2023-06-01 22:40 ` Glen Choo
2023-06-01 22:57 ` Fraser Hanson [this message]
2023-06-19 18:40 ` Fraser Hanson
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=CA+3o5aNgChKi-m6F_sYr4Sc+VXP-K2BCMpTpY8Km+kH5u9tkCQ@mail.gmail.com \
--to=fraser.hanson@gmail.com \
--cc=chooglen@google.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).