mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <>
To: "Tim Renouf (open source)" <>
Cc: Git Mailing List <>
Subject: Re: bug report: git checkout deletes worktree file even though it is excluded by sparse-checkout
Date: Fri, 28 May 2021 15:44:45 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


On Fri, May 28, 2021 at 1:46 PM Tim Renouf (open source)
<> wrote:
> Hi all
> I have a bug report: git checkout deletes a worktree file even though it is excluded by sparse-checkout, even if it is dirty.
> Watch this (starting in an empty directory):
> $ git init
> Initialised empty Git repository in /mnt/amd/home/trenouf/amd/tmp/git/.git/
> $ echo file1 >file1; echo file2 >file2
> $ git add file1 file2
> $ git commit -m"commit 1"
> [master (root-commit) 4f7035d] commit 1
>  2 files changed, 2 insertions(+)
>  create mode 100644 file1
>  create mode 100644 file2
> $ git rm file2
> rm 'file2'
> $ git commit -m"rm file2"
> [master d025c99] rm file2
>  1 file changed, 1 deletion(-)
>  delete mode 100644 file2
> $ git checkout master~1
> HEAD is now at 4f7035d commit 1
> $ git sparse-checkout set /file1
> $ ls
> file1
> $ echo dirty >file2
> $ ls
> file1  file2
> $ git checkout master
> Previous HEAD position was 4f7035d commit 1
> Switched to branch 'master'
> $ ls
> file1
> I set up sparse-checkout to include only file1, not file2. file2 is now not in the worktree, even though it is in the commit I am checked out at. Then I create file2 with arbitrary content. Then a git checkout switching to the commit where file2 is removed also deletes it from the worktree.
> I assert that file2 should be left untouched by that checkout, because it is excluded by sparse-checkout. I guess file2 had its skip-worktree bit set before the checkout that removed it from the index; that should stop it being deleted in the worktree.
> To be clear, I expect that last “ls” to still show “file1  file2”.
> Thank you for your attention if you have got this far.

Thanks for the report.  It's another example of how
"skip-worktree-means-treat-the-file-as-matching-head" causes
confusion.  You can find more issues with
present-despite-skip-worktree files at,
including reasons they come up more often than you'd think.

We do need to get these fixed up, though I don't want to step on
Stolee's toes with his sparse-index work, and I'm hesitant to open new
big projects until merge-ort is complete.

> -tpr
> [System Info]
> git version:
> git version 2.31.1
> cpu: x86_64
> no commit associated with this build
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> uname: Linux 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64
> compiler info: gnuc: 9.3
> libc info: glibc: 2.31
> $SHELL (typically, interactive shell): /bin/bash

  reply	other threads:[~2021-05-28 22:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 20:14 bug report: git checkout deletes worktree file even though it is excluded by sparse-checkout Tim Renouf (open source)
2021-05-28 22:44 ` Elijah Newren [this message]
2021-06-01 18:31   ` [PATCH] unpack-trees: add core.sparseCheckoutRmFiles config Tim Renouf
2021-06-02  2:00     ` Derrick Stolee
2021-06-02  2:32       ` Junio C Hamano
2021-06-02  5:53         ` Elijah Newren
2021-06-02  6:13           ` Tim Renouf (open source)
2021-06-02 23:41             ` Elijah Newren
2021-06-05 15:33               ` Tim Renouf (open source)
2021-06-02  1:37 ` bug report: git checkout deletes worktree file even though it is excluded by sparse-checkout Derrick Stolee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).