From: Junio C Hamano <junkio@cox.net>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: junkio@cox.net
Cc: git@vger.kernel.org
Subject: Re: [PATCH] fetch-pack: avoid packing reachable objects.
Date: Tue, 25 Oct 2005 22:07:11 -0700 [thread overview]
Message-ID: <7v7jc0c1ds.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051026042632.GA3059@delft.aura.cs.cmu.edu> (Jan Harkes's message of "Wed, 26 Oct 2005 00:26:32 -0400")
Jan Harkes <jaharkes@cs.cmu.edu> writes:
> Mark remote commits that were found in the alternate repository as
> COMPLETE and avoid unnecessary packing of already available objects.
Sorry, this is wrong (we made this mistake twice already). The
mere existence of that object in the local repository does not
necessarily mean we have everything that is reachable from it.
The rule is that we only trust local refs. Anything that are
reachable from them are known to be complete. And after a
successful fetch, we update local refs. The existence of an
object is a strong _hint_ that it _might_ be complete, but
nothing more.
Think of a case where you tried to fetch via commit walker and
got things reachable from the then-current ref, and the
object you are marking as COMPLETE (maybe in pack) is a remnant
of that failed fetch, which was killed before completing. You
might have complete history starting from the then-current
commit back to that commit, but there is no guarantee that you
can further tangle the history back and find everything needed.
prev parent reply other threads:[~2005-10-26 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 4:26 [PATCH] fetch-pack: avoid packing reachable objects Jan Harkes
2005-10-26 5:07 ` Junio C Hamano [this message]
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=7v7jc0c1ds.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=jaharkes@cs.cmu.edu \
/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