public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Yuri <yuri@rawbw.com>
To: 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 16:27:32 -0700	[thread overview]
Message-ID: <e8feffd0-ba6d-4aae-8c80-3d6482896b08@rawbw.com> (raw)
In-Reply-To: <xmqqikygzdgk.fsf@gitster.g>

On 6/10/24 14:37, Junio C Hamano wrote:
> But .nfs* files are not something you as an application are not 
> supposed to touch, so a directory that still contains one cannot be 
> removed, either. It's a limitation (I wouldn't call it a "bug") of 
> NFS. You can kill the process (or wait until they exit) holding the 
> file open and then run "clean -df" again, perhaps.


With the '-f' the user tells git to remove all, and if this doesn't work 
git should tell the user that this didn't work for the .nfsNNNNNNN file 
and for the directory as well.


Why is git quiet about leaving the files. It should complain.

Or maybe there should be a verbosity option, like -v 10, that would make 
git complain about such things.







Thanks,

Yuri


  reply	other threads:[~2024-06-10 23:27 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 [this message]
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'
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=e8feffd0-ba6d-4aae-8c80-3d6482896b08@rawbw.com \
    --to=yuri@rawbw.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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