public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] reachable: only mark local objects as recent
Date: Fri, 27 Mar 2015 12:00:05 -0700	[thread overview]
Message-ID: <xmqqa8yyw9je.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150327113240.GA7781@peff.net> (Jeff King's message of "Fri, 27 Mar 2015 07:32:41 -0400")

Jeff King <peff@peff•net> writes:

> It is possible that we may drop an object that is depended
> upon by another object in the alternate. For example,
> imagine two repositories, A and B, with A pointing to B as
> an alternate. Now imagine a commit that is in B which
> references a tree that is only in A. Traversing from recent
> objects in B might prevent A from dropping that tree. But
> this case isn't worth covering. Repo B should take
> responsibility for its own objects. It would never have had
> the commit in the first place if it did not also have the
> tree, and assuming it is using the same "keep recent chunks
> of history" scheme, then it would itself keep the tree, as
> well.

In other words, if you have a loop in dependency chain among
alternate repositories, your set-up is broken by definition.

Which makes sense to me.

Thanks.

  reply	other threads:[~2015-03-27 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 11:32 [PATCH] reachable: only mark local objects as recent Jeff King
2015-03-27 19:00 ` Junio C Hamano [this message]
2015-04-17 13:28   ` Jeff King
2015-04-17 17:18     ` Junio C Hamano

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=xmqqa8yyw9je.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=peff@peff$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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