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

Re: [PATCH] reset: behave correctly with sparse-checkout

From
Derrick Stolee <stolee@gmail.com>
Date
Sep 28, 2021, 20:20 UTC
Message-ID
<bd7d6515-e1ca-9646-5e73-5594d7991ec3@gmail.com>
In-Reply-To
<pull.1047.git.1632842421213.gitgitgadget@gmail.com>
On 9/28/2021 11:20 AM, Derrick Stolee via GitGitGadget wrote:
Show 10 quoted lines
> From: Kevin Willford <kewillf@microsoft.com>
> 
> When using the sparse checkout feature, 'git reset' will add entries to
> the index that will have the skip-worktree bit off but will leave the
> working directory empty. File data is lost because the index version of
> the files has been changed but there is nothing that is in the working
> directory. This will cause the next 'git status' call to show either
> deleted for files modified or deleting or nothing for files added. The
> added files should be shown as untracked and modified files should be
> shown as modified.

Sorry for the noise, but hold off on this patch. It will be joining a larger series involving getting 'git reset' working with the sparse index.

Thanks, -Stolee

Previous: Derrick Stolee via GitGitGadget
Message 2 of 2 in “reset: behave correctly with sparse-checkout”
  1. reset: behave correctly with sparse-checkoutDerrick Stolee via GitGitGadget, Sep 28, 2021
  2. Derrick StoleeSep 28, 2021

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.