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

Re: sparse support in pu

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Aug 17, 2009, 10:36 UTC
Message-ID
<4A8932BB.7030002@viscovery.net>
In-Reply-To
<fcaeb9bf0908170321o43fa4a6bv95dd78ff7889686f@mail.gmail.com>
Nguyen Thai Ngoc Duy schrieb:
Show 10 quoted lines
> [I haven't read the rest of the mail, will read it through later]
> 
> On Mon, Aug 17, 2009 at 3:49 PM, <skillzero@gmail.com> wrote:
>> It would be nice if .git/info/sparse is there by default (like
>> .git/info/exclude) with some commented out instructions (also like
>> .git/info/exclude).
> 
> No it can't be there by default. An empty .git/info/sparse means clear
> assume-unchanged bit out of all files in index. It's not the same as
> lacking .git/info/sparse (which does disable sparse checkout feature).

Huh? Shouldn't the meaning of .git/info/sparse be: "the files mentioned in this file are not checked out." That is, if the file is empty, then no file is not checked out, IOW, all files are checked out.

In order to advocate my earlier proposal: Name the file .git/info/phantoms, then it's clear: "The files mentioned here are phantoms" - they exist in the index, but not in the worktree; no phantoms means that everything is checked out.

-- Hannes
Previous: Nguyen Thai Ngoc DuyNext: Nguyen Thai Ngoc Duy
Message 10 of 21 in “sparse support in pu”
  1. skillzero@gmail.comAug 17, 2009
  2. Nguyen Thai Ngoc DuyAug 17, 2009
  3. skillzero@gmail.comAug 17, 2009
  4. Johannes SchindelinAug 17, 2009
  5. skillzero@gmail.comAug 17, 2009
  6. Johannes SixtAug 17, 2009
  7. Johannes SchindelinAug 17, 2009
  8. Nguyen Thai Ngoc DuyAug 17, 2009
  9. Nguyen Thai Ngoc DuyAug 17, 2009
  10. Johannes SixtAug 17, 2009
  11. Nguyen Thai Ngoc DuyAug 17, 2009
  12. Johannes SixtAug 17, 2009
  13. Nguyen Thai Ngoc DuyAug 17, 2009
  14. Johannes SchindelinAug 17, 2009
  15. Peter HarrisAug 17, 2009
  16. Johannes SchindelinAug 17, 2009
  17. Peter HarrisAug 17, 2009
  18. Junio C HamanoAug 17, 2009
  19. Johannes SchindelinAug 17, 2009
  20. Nguyen Thai Ngoc DuyAug 17, 2009
  21. James PickensAug 17, 2009

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.