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

Re: git sparse checkout repo size

From
GPgaoyong pan <pan.gaoyong@gmail.com>
Date
Jul 18, 2011, 11:54 UTC
Message-ID
<CALf5Ac3DcoB+Psgwys6NNOmTcyGmKj5dKhR7K8ardF6MsCCDwA@mail.gmail.com>
In-Reply-To
<CACsJy8C=LdcaQbc46ssc5=tTXyA-U4N4FAsqjnPyEqwYZuO4LA@mail.gmail.com>
2011/7/18 Nguyen Thai Ngoc Duy <pclouds@gmail.com>:
Show 7 quoted lines
> The ideal
> solution would be narrow/sparse clone where you only fetch history of
> your two files (plus necessary trees and commits) but that won't come
> this year.
> --
> Duy
>

I need to push back so sparse clone is the best solution, it must be very difficult to implement so it won't be released in this year?

-- 
Best Regards
Linux user #384184
@ http://counter.li.org/
Previous: Nguyen Thai Ngoc DuyNext: Nguyen Thai Ngoc Duy
Message 3 of 4 in “Re: git sparse checkout repo size”
  1. gaoyong panJul 18, 2011
  2. Nguyen Thai Ngoc DuyJul 18, 2011
  3. gaoyong panJul 18, 2011
  4. Nguyen Thai Ngoc DuyJul 18, 2011

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.