From: Jonathan Tan <jonathantanmy@google.com>
To: nospam@cheerful.com
Cc: git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>
Subject: Re: [BUG/FEATURE] Git pushing and fetching many more objects than strictly required
Date: Fri, 8 Nov 2019 10:47:23 -0800 [thread overview]
Message-ID: <20191108184723.246596-1-jonathantanmy@google.com> (raw)
In-Reply-To: <bc43c70e-861d-425d-d7c4-73a3e25b7383@cheerful.com>
> $ git fetch --all
> Fetching origin
> remote: Enumerating objects: 29507, done.
> remote: Counting objects: 100% (29507/29507), done.
> remote: Compressing objects: 100% (33/33), done.
> remote: Total 53914 (delta 29478), reused 29500 (delta 29471), pack-reused 24407
> Receiving objects: 100% (53914/53914), 31.90 MiB | 111.00 KiB/s, done.
> Resolving deltas: 100% (42462/42462), completed with 7382 local objects.
> --
>
> $ git push -v origin 'refs/replace/*:refs/replace/*'
> Pushing to XXXX
> Enumerating objects: 2681, done.
> Counting objects: 100% (2681/2681), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (1965/1965), done.
> Writing objects: 100% (2582/2582), 1.96 MiB | 1024 bytes/s, done.
> Total 2582 (delta 95), reused 1446 (delta 58)
> remote: Resolving deltas: 100% (95/95), completed with 33 local objects.
> To XXXX
> * [new branch] refs/replace/XXXX -> refs/replace/XXXX
Could you verify that refs/replace/XXXX (or one of its close ancestors)
was fetched by the "git fetch --all" command? "--all" fetches all
remotes, not all refs.
next prev parent reply other threads:[~2019-11-08 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:06 [BUG/FEATURE] Git pushing and fetching many more objects than strictly required Paul van Loon
2019-11-08 18:47 ` Jonathan Tan [this message]
2019-11-08 20:54 ` Paul van Loon
2019-11-08 21:21 ` Jeff King
2019-11-12 13:39 ` Paul van Loon
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
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 \
--in-reply-to=20191108184723.246596-1-jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=nospam@cheerful.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).