Re: Unresolved issues #2 (shallow clone again)

From: Junio C Hamano <junkio@cox.net>
Date: May 8, 2006, 02:54 UTC
Message-ID: <7vy7xdgram.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <e3ksoq$is$1@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> writes:

Show 9 quoted lines

> 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.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.