From: Bagas Sanjaya <firstname.lastname@example.org>
Subject: Argument list too long when fetching many missing objects from partial clone
Date: Mon, 1 Mar 2021 20:18:29 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
I'm poking around with partial clone. On my local server on my computer
I have full clone of Git (git.git) repo.
I do partial clone from that server as remote (which is actually on the same
git clone https://my-local-server.git/myself/git.git --filter=blob:none
Inside the partial clone, I tried to convert it to full clone. First, I gather
list of missing objects:
git rev-list --objects --all --missing=print | grep -oP '^\?\K\w+' > .git/missing.list
Then I fetched those:
git fetch origin $(cat .git/missing.list)
What did you expect to happen? (Expected behavior)
All missing objects fetched successfully
What happened instead? (Actual behavior)
-bash: /opt/git/bin/git: Argument list too long
What's different between what you expected and what actually happened?
Anything else you want to add:
I think the problem lies on how to feed list of 110K+ objects to `git fetch`.
Note: Both the local server and the computer use Git 2.30.1
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
git version 2.30.1
built from commit: 773e25afc41b1b6533fa9ae2cd825d0b4a697fad
uname: Linux 5.10.11-kernelorg-upstream-generic #1 SMP Fri Jan 29 12:56:19 WIB 2021 x86_64
compiler info: gnuc: 9.3
libc info: glibc: 2.31
$SHELL (typically, interactive shell): /bin/bash
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2021-03-01 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 13:18 Bagas Sanjaya [this message]
2021-03-01 19:21 ` Jeff Hostetler
2021-03-01 19:22 ` Bryan Turner
2021-03-02 6:55 ` Bagas Sanjaya
2021-03-03 0:42 ` brian m. carlson
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this inbox:
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).