Re: Pushing/fetching from/into a shallow-cloned repository

From: Duy Nguyen <pclouds@gmail.com>
Date: Apr 19, 2013, 11:22 UTC
Message-ID: <CACsJy8DUZYuGO=4WL-uyszxvhvwyuz4=SvW6O0O+5O+XZUfDmg@mail.gmail.com>
In-Reply-To: <8BCCECD4CEEA4028AD97B851099F4C5E@PhilipOakley>

On Fri, Apr 19, 2013 at 6:27 AM, Philip Oakley <philipoakley@iee.org> wrote:

Show 17 quoted lines

> From: "Konstantin Khomoutov" <kostix+git@007spb.ru>
>> So I observe pushing/fetching works OK at least for a simple case like
>> this one.
>>
>> Hence I'd like to ask: if the manual page is wrong or I'm observing
>> some corner case?
>> --
>
> The manual is deliberately misleading.
> The problem is that the depth is a movable feast that depends on how far the
> branches have progressed.
> The DAG will be missing the historic merge bases, and in some scenarios can
> form disconnected runs of commits. The ref negotiation can also be a
> problem.
>
> The git\Documentation\technical\shallow.txt has some extra details on
> issues.

With recent improvements in index-pack, I think we can be certain that all gaps are caught. So either it works or it does not. It cannot lead to an incomplete repository. At least for git and smart http transports. So I'm inclined to lift the limitation for these transports. Missing merge bases remains a limitation the user should be aware of, of course. -- Duy