git/list[1] front-page[2] threads[3] people[4] search[5] about
 

'sparse' clone idea

From
Jakub Narebski <jnareb@gmail.com>
Date
Jun 14, 2006, 08:23 UTC
Message-ID
<e6oh2g$ngh$1@sea.gmane.org>

I wonder if 'sparse clone' idea described below would avoid the most difficult part of 'shallow clone' idea, namely the [sometimes] need to un-cauterize history. See: (<7vac8lidwi.fsf@assigned-by-dhcp.cox.net>).

'sparse clone' begins like 'shallow clone': full history is copied down to specified point of history (cut-off or cauterization point for shallow clone), but instead of cauterizing the history from that point downwards, the history is simplified using grafts.

In the sparse part we need:
 * all commits pointed by tags (if we clone/copy tags) 
   and other refs (if we clone/copy those tags)
 * merge bases for all commits in full, and in the sparse part,
   _including_ merge bases themselves
 * all roots

Commits in sparse part would be connected like in original history, only skipping "uniteresting" commits.

Thoughts? Comments?
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Next: Johannes Schindelin
Message 1 of 3 in “'sparse' clone idea”
  1. Jakub NarebskiJun 14, 2006
  2. Johannes SchindelinJun 14, 2006
  3. Jakub NarebskiJun 14, 2006

Read the whole thread, see it on lore, or plain text.

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