Re: [gentoo-project] Council / Git Migration Agenda

[Rich Freeman <rich0@gentoo.org>]

On Tue, Oct 7, 2014 at 7:00 AM, Anthony G. Basile <blueness@gentoo.org> wrote:
> On 10/07/14 06:58, Rich Freeman wrote:
>>
>> On Tue, Oct 7, 2014 at 3:57 AM, Dirkjan Ochtman <djc@gentoo.org> wrote:
>>>
>>> Can we do that without requiring the git replace stuff? E.g. have
>>> dev.git be a shallow clone of a joined-history.git?
>>>
>> That was the original plan I suggested abandoning in my email, for the
>> reasons stated in my email.  None of them had to do with repository
>> size, actually, though having a repository with an obsolete 1.5GB
>> history embedded certainly isn't ideal.
>>
>
> What does a shallow clone mean exactly?
>

It means a git repository that does not contain the full history.
That is, if you take one of the heads, such as master, and follow the
parent commits back, you eventually reach a commit that isn't actually
in the repository.  Git now has a --depth option to allow making them
easily in a clone operation.

Not all operations may work on them, but I've found conflicting
stories online about what is/isn't possible.  Generally you would
probably want full clones in all the official repositories to avoid
issues.

--
Rich