Re: [BUG?] After 'git checkout', files deleted upstream are left in the working directory as untracked

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 12, 2020, 11:10 UTC
Message-ID: <nycvar.QRO.7.76.6.2010121306470.50@tvgsbejvaqbjf.bet>
In-Reply-To: <3D3C5F5D-830E-4EC7-A527-DC595D983BB2@gmail.com>

Hi Philippe,

On Sat, 10 Oct 2020, Philippe Blain wrote:

Show 9 quoted lines

> $ git status # the following is what is shown in my old clone
> On branch other-branch
> Untracked files:
>   (use "git add <file>..." to include in what will be committed)
>
> 	git-legacy-stash
> 	git-remote-testsvn
> 	t/helper/test-line-buffer
> 	t/helper/test-svn-fe

These files were generated previously, but are no longer generated (`legacy-stash` was retired in favor of the built-in `stash`, `remote-testsvn` was dropped because it languished for long enough without anybody picking it back up, and the test helpers were necessary to test `test-svn`).

Since they are no longer generated, those build products are no longer desired.

And you don't see them in a fresh clone because they were only compiled in previous revisions.

So this works as expected.

What you will want to do is to run `git clean -dn` to see what `clean` would remove, and once satisfied that it's all good, actually remove the files using `git clean -df`.

Ciao, Dscho