Re: Unresolved issues #2 (shallow clone again)
Show 18 quoted lines
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> Wouldn't it be easier (sorry, no code yet) to have the following:
>>
>> I WANT to have these
>> I HAVE these
>> These are GRAFT PARENTLESS
>>
>> with the target side sending list of all parentless commits in the
>> ... The source side will then do the grafting 'in memory' and
>> send the packs like normal, only with those cauterizing grafts in place.
>
> I think that is essentially the outline of shallow clone
> proposal, except that you have to be careful and take not just
> "parentless" but other grafts (e.g. one that removes one parent
> from a merge commit to pretend that a side branch did not exist)
> into account as well. I do not remember if I already coded it
> or not -- I might have.
So, let it be all grafts removing some or all parents from commit.
And that proposal would work I think also for the fetch, not only clone.
--
Jakub Narebski
Warsaw, Poland