From: Junio C Hamano <gitster@pobox.com>
To: David Howells <dhowells@redhat.com>
Cc: git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: GIT BUG? GIT occasionally redownloads its entire data set
Date: Mon, 23 Mar 2009 19:17:10 -0700 [thread overview]
Message-ID: <7vskl34qc9.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <28707.1237855543@redhat.com> (David Howells's message of "Tue, 24 Mar 2009 00:45:43 +0000")
David Howells <dhowells@redhat.com> writes:
> to v2.6.29. I've attached the command output for reference.
Version of git used, and the .git/config ([remote "origin"] section)?
> warthog>git-pull
> remote: Counting objects: 447, done.
> remote: Compressing objects: 100% (57/57), done.
> remote: Total 266 (delta 216), reused 254 (delta 207)
> Receiving objects: 100% (266/266), 37.94 KiB, done.
> Resolving deltas: 100% (216/216), completed with 105 local objects.
> warning: no common commits
> remote: Counting objects: 1075436, done.
> remote: Compressing objects: 100% (176743/176743), done.
> remote: Total 1075436 (delta 896164), reused 1072243 (delta 893708)
> Receiving objects: 100% (1075436/1075436), 260.71 MiB | 307 KiB/s, done.
> Resolving deltas: 100% (896164/896164), done.
>>From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
This is intereseting because it shows that two separate transfer happened
back to back, which I do not think is what recent git does.
We used to first grab the objects reachable from primary refs (presumably
[remote "origin"] fetch = refs/heads/*:refs/remotes/origin/*) and then
turned around to ask for tags that possibly point at commits we freshly
obtained during the first transfer (i.e. the ones reachable from the tip
of "master"). In such an ancient version I vaguely recall some bugs fixed
before we stopped doing this two-stage transfer altogether, but I do not
recall offhand if a bug that loses track of what it just downloaded (which
is what your description suggests) was among them.
Rings a bell, anybody?
next prev parent reply other threads:[~2009-03-24 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 0:45 GIT BUG? GIT occasionally redownloads its entire data set David Howells
2009-03-24 2:17 ` Junio C Hamano [this message]
2009-03-24 2:53 ` Dmitry Potapov
2009-03-24 6:02 ` Junio C Hamano
2009-03-24 9:15 ` David Howells
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=7vskl34qc9.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=dhowells@redhat.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 NNTP newsgroup(s).