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

Re: What's cooking in git.git (Oct 2008, #03; Tue, 14)

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Oct 15, 2008, 11:54 UTC
Message-ID
<fcaeb9bf0810150454g572f6147w6a61d770ba28e808@mail.gmail.com>
In-Reply-To
<7v8wsq7rt5.fsf@gitster.siamese.dyndns.org>
On 10/15/08, Junio C Hamano <gitster@pobox.com> wrote:
Show 18 quoted lines
>  [Stuck Topics]
>
>  * nd/narrow (Wed Oct 1 11:04:09 2008 +0700) 9 commits
>   - grep: skip files outside sparse checkout area
>   - checkout_entry(): CE_NO_CHECKOUT on checked out entries.
>   - Prevent diff machinery from examining worktree outside sparse
>    checkout
>   - ls-files: Add tests for --sparse and friends
>   - update-index: add --checkout/--no-checkout to update
>    CE_NO_CHECKOUT bit
>   - update-index: refactor mark_valid() in preparation for new options
>   - ls-files: add options to support sparse checkout
>   - Introduce CE_NO_CHECKOUT bit
>   - Extend index to save more flags
>
>  Recently updated with a repost.  Shawn says he's been too swamped at
>  day-job to actively review the series.  There has been some discussion on
>  list about it so its not stalled, but it needs more eyeballs.

Just a bit of update. I'm still working on the second half. Code change is even more than this, so I will wait until the first half gets reviewed and accepted before sending the rest.

BTW, in the first half, unpack_trees()-related commands may refuse to work if there is orphaned/stale entries in working directory (verify_*() functions still look at working directory no matter whether entries are no-checkout). Those entries are troublesome anyway so encouraging people to clean them out is, IMHO, a good idea, rather than fixing unpack_trees() to ignore them.

-- 
Duy
Previous: Johannes SixtNext: Thomas Rast
Message 5 of 6 in “What's cooking in git.git (Oct 2008, #03; Tue, 14)”
  1. Junio C HamanoOct 14, 2008
  2. Stephen HabermanOct 15, 2008
  3. Johannes SixtOct 15, 2008
  4. Johannes SixtOct 18, 2008
  5. Nguyen Thai Ngoc DuyOct 15, 2008
  6. Thomas RastOct 16, 2008

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.