From: "'Yuri'" <yuri@rawbw.com>
To: rsbecker@nexbridge.com, "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Git Mailing List'" <git@vger.kernel.org>
Subject: Re: [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files
Date: Mon, 10 Jun 2024 18:22:29 -0700 [thread overview]
Message-ID: <b8f8fa08-e4a0-4755-99f0-9311b05945dd@rawbw.com> (raw)
In-Reply-To: <0eef01dabb9d$70c99690$525cc3b0$@nexbridge.com>
On 6/10/24 18:19, rsbecker@nexbridge.com wrote:
> That is what I suspected. I am suspecting that git does not see the
> .nfsNNNN file when it is performing the clean. I think NFS creates the
> file after git does the scan, so as far as git is concerned, there is
> no .nfsNNNN file until after the operation completes. NFS puts the
> file there independent of git, so git does not even know about it.
> Does a second git clean -df . remove the .nfsNNNN file and put a new
> one, with a different name, in place?
No, *only* the .nfsXXXX file exists in the xx directory when git runs.
Yuri
next prev parent reply other threads:[~2024-06-11 1:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 18:36 [BUG] "git clean -df ." silently doesn't delete folders with stale .nfs* files Yuri
2024-06-10 19:58 ` Junio C Hamano
2024-06-10 20:08 ` Yuri
2024-06-10 21:37 ` Junio C Hamano
2024-06-10 23:27 ` Yuri
2024-06-10 23:55 ` rsbecker
2024-06-11 0:29 ` Junio C Hamano
2024-06-11 1:09 ` 'Yuri'
2024-06-11 1:19 ` rsbecker
2024-06-11 1:22 ` 'Yuri' [this message]
2024-06-11 1:46 ` Chris Torek
2024-06-11 6:48 ` Jeff King
2024-06-11 7:43 ` 'Yuri'
2024-06-13 8:09 ` Gabor Gombas
2024-06-13 9:21 ` 'Yuri'
2024-06-11 13:48 ` rsbecker
2024-06-11 17:46 ` 'Yuri'
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b8f8fa08-e4a0-4755-99f0-9311b05945dd@rawbw.com \
--to=yuri@rawbw.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rsbecker@nexbridge.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox