From: Junio C Hamano <junkio@cox.net>
To: Alexandre Julliard <julliard@winehq.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>, git@vger.kernel.org
Subject: Re: Shallow clone
Date: Sun, 12 Nov 2006 00:16:40 -0800 [thread overview]
Message-ID: <7vu015f5av.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 87zmaynl18.fsf@wine.dyndns.org
Alexandre Julliard <julliard@winehq.org> writes:
> There's also a problem with the packing, a clone --depth 1 currently
> results in a pack that's about 3 times as large as it should be.
That's interesting.
: gitster; git clone -n --depth 1 git://127.0.0.1/git.git victim-001
remote: Generating pack...
remote: Done counting 6246 objects.
remote: Deltifying 6246 objects.
remote: 100% (6246/6246) done
Indexing 6246 objects.
remote: Total 6246, written 6246 (delta 3106), reused 4313 (delta 3106)
100% (6246/6246) done
Resolving 3106 deltas.
100% (3106/3106) done
: gitster; cd victim-001
: gitster; ls -lh .git/objects/pack/
total 9.6M
drwxrwsr-x 2 junio src 4.0K 2006-11-11 23:52 ./
drwxrwsr-x 4 junio src 4.0K 2006-11-11 23:52 ../
-r--r--r-- 1 junio src 148K 2006-11-11 23:52 pack-f5f88d83....idx
-r--r--r-- 1 junio src 9.5M 2006-11-11 23:52 pack-f5f88d83....pack
Repacking immediately after cloning brings it down to what is
expected.
: gitster; git repack -a -d -f
Generating pack...
Done counting 6246 objects.
Deltifying 6246 objects.
100% (6246/6246) done
Writing 6246 objects.
100% (6246/6246) done
Total 6246, written 6246 (delta 4815), reused 1407 (delta 0)
Pack pack-f5f88d83524213e3ab05697ff75f245b1ef9081a created.
: gitster; ls -lh .git/objects/pack/
total 2.8M
drwxrwsr-x 2 junio src 4.0K 2006-11-11 23:53 ./
drwxrwsr-x 4 junio src 4.0K 2006-11-11 23:52 ../
-rw-rw-r-- 1 junio src 148K 2006-11-11 23:53 pack-f5f88d83....idx
-rw-rw-r-- 1 junio src 2.6M 2006-11-11 23:53 pack-f5f88d83....pack
In any case, after this "shallow" stuff, repeated "fetch --depth
99" seems to fetch 0 object and 3400 objects alternately, and
the shallow file alternates between 900 bytes and 11000 bytes.
We would need to take a deeper look into what this series does,
before moving it to 'next'.
next prev parent reply other threads:[~2006-11-12 8:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 3:21 What's in git.git Junio C Hamano
2006-11-08 4:13 ` David Lang
2006-11-08 16:40 ` Shallow clone [Was Re: What's in git.git ] Aneesh Kumar K.V
2006-11-08 17:59 ` Aneesh Kumar K.V
2006-11-09 4:04 ` Shallow clone Junio C Hamano
2006-11-09 4:17 ` Aneesh Kumar
2006-11-11 13:57 ` Alexandre Julliard
2006-11-12 8:16 ` Junio C Hamano [this message]
2006-11-12 17:59 ` Sergey Vlasov
2006-11-12 21:59 ` Junio C Hamano
2006-11-13 5:29 ` Junio C Hamano
2006-11-12 13:12 ` Shallow clone [Was Re: What's in git.git ] Petr Baudis
2006-11-12 20:04 ` Shallow clone Junio C Hamano
2006-11-09 2:28 ` What's in git.git Horst H. von Brand
2006-11-09 2:54 ` Junio C Hamano
2006-11-09 3:04 ` Junio C Hamano
2006-11-09 3:45 ` Dave Dillow
2006-11-12 22:25 ` Johannes Schindelin
2006-11-08 7:40 ` Jakub Narebski
2006-11-08 7:59 ` Junio C Hamano
2006-11-08 7:58 ` Jakub Narebski
2006-11-08 8:26 ` Junio C Hamano
2006-11-08 14:51 ` Petr Baudis
2006-11-09 0:02 ` Junio C Hamano
[not found] <CAEfjWpHhLKpghGRFtzstndk_vYMkLSLAGfXx8agoQmakC-6Otg@mail.gmail.com>
2014-08-19 11:11 ` Fwd: Shallow clone Steven Evergreen
2014-08-19 12:01 ` Duy Nguyen
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=7vu015f5av.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=julliard@winehq.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.
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).