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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Philippe,

On Sat, 10 Oct 2020, Philippe Blain wrote:

> $ 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




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux