From: Kevin Daudt <me@ikke.info>
To: Jiri Slaby <jslaby@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: Fetching 24 Linux commits = 1.2 GiB
Date: Wed, 15 Apr 2020 12:52:47 +0200 [thread overview]
Message-ID: <20200415105247.GA1710231@alpha> (raw)
In-Reply-To: <b7f5bfb9-61fb-2552-4399-b744428728e4@suse.cz>
On Wed, Apr 15, 2020 at 10:01:46AM +0200, Jiri Slaby wrote:
> Hi,
>
> I was at 8f3d9f354286 of:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>
> I did git remote update today and it fetched:
> Receiving objects: 100% (7330823/7330823), 1.20 GiB
> It updated master: 8f3d9f354286..8632e9b5645b, that is 24 small commits.
>
> One colleague of mine fetched 1324 commits:
> Receiving objects: 100% (6820/6820), 4.21 MiB | 6.70 MiB/s, done.
> Resolving deltas: 100% (5114/5114), completed with 1035 local objects.
> From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
> 7e63420847ae..8632e9b5645b master -> origin/master
>
> Another colleague fetched the same what I and:
> Receiving objects: 100% (7330823/7330823), 1.20 GiB
> too.
>
> I did git gc --prune && git prune now and I am at 1.7G back from 3.5 G.
>
> Is that a bug? What info should I provide?
>
> thanks,
> --
> js
> suse labs
Not as big as you report, but I recall a user on IRC (guardian) was
wondering as well why a packfile was 240MB while they claimed that the
objects were committed months ago.
next prev parent reply other threads:[~2020-04-15 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 8:01 Fetching 24 Linux commits = 1.2 GiB Jiri Slaby
2020-04-15 8:11 ` Andreas Schwab
2020-04-15 8:16 ` Jiri Slaby
2020-04-15 8:23 ` Andreas Schwab
2020-04-15 8:27 ` Jiri Slaby
2020-04-15 8:34 ` Andreas Schwab
2020-04-15 10:52 ` Kevin Daudt [this message]
2020-04-15 13:56 ` Konstantin Ryabitsev
2020-04-15 15:08 ` Junio C Hamano
2020-04-15 15:16 ` Jeff King
2020-04-15 18:52 ` Jonathan Nieder
2020-05-20 8:53 ` Andreas Schwab
2020-05-20 8:57 ` Andreas Schwab
2020-05-20 10:05 ` Michal Suchánek
2020-05-20 10:34 ` Andreas Schwab
2020-05-20 19:40 ` Jeff King
2020-05-25 18:22 ` Lukas Wunner
2020-05-25 18:37 ` Junio C Hamano
2020-04-16 6:31 ` Jiri Slaby
2020-04-21 10:02 ` Martin Wilck
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=20200415105247.GA1710231@alpha \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=jslaby@suse.cz \
/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.