git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: [BUG?] After 'git checkout', files deleted upstream are left in the working directory as untracked
Date: Sun, 11 Oct 2020 12:19:17 -0400	[thread overview]
Message-ID: <7F30E2AB-D742-4581-9AF8-6138A45A3F22@gmail.com> (raw)
In-Reply-To: <8f88733f-4f20-6215-00a8-de3024b8c4cb@kdbg.org>

Hi Johannes, 

> Le 11 oct. 2020 à 02:58, Johannes Sixt <j6t@kdbg.org> a écrit :
> 
> Am 10.10.20 um 18:43 schrieb Philippe Blain:
>> The thing is, I can't reproduce it on a fresh clone. If I could, this would be a reproducer:
>> 
>> ```
>> $ git clone git@github.com:phil-blain/git.git && cd git
>> $ git checkout stale-branch
>> $ git checkout other-branch
>> $ 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
>> 
>> nothing added to commit but untracked files present (use "git add" to track)
>> ```
> 
> This is normal. These 4 files are build products and were never
> committed files. They had been mentioned in .gitignore in the past, but
> are not anymore.

Oops, I should've checked that. Thanks for answering!

Philippe.


  reply	other threads:[~2020-10-11 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10 16:43 [BUG?] After 'git checkout', files deleted upstream are left in the working directory as untracked Philippe Blain
2020-10-11  6:58 ` Johannes Sixt
2020-10-11 16:19   ` Philippe Blain [this message]
2020-10-12 11:10 ` Johannes Schindelin

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7F30E2AB-D742-4581-9AF8-6138A45A3F22@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://80x24.org/mirrors/git.git

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).