All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Turner <dturner@twopensource.com>
Cc: git@vger.kernel.org, David Turner <dturner@twitter.com>
Subject: Re: [PATCH] builtin/clean.c: Handle disappearing files
Date: Sat, 16 May 2015 12:21:04 -0700	[thread overview]
Message-ID: <xmqqwq08e3bz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1431713612.17436.27.camel@ubuntu> (David Turner's message of "Fri, 15 May 2015 14:13:32 -0400")

David Turner <dturner@twopensource.com> writes:

> So maybe we should just move the lstat below the pathspec check.  This
> is probably faster in some cases anyway.  What do you think?

I also was wondering about the placement of that lstat; because
having it before the pathspec filtering didn't make sense to me at
all.  If we are not told to clean some parts of the tree, we really
shouldn't be looking at that part of the tree.  I think such a
change is desirable and the justification of the change should be
based solely on the above---limit first and then check, don't check
what we were not told to look at.

And if such a change lets you solve your original issue, that is a
nice side effect I am happy to see.  By excluding the paths that are
unstable (because other processes randomly muck with them without
coordinating with the user) explicitly when running "git clean", the
user _is_ saying that s/he is aware of the issue and is actively
avoiding modifications by the third-party would not get in the way,
so I wouldn't call that sweeping it under the rug, like I did for
your original one.

Thanks.

      reply	other threads:[~2015-05-16 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 21:16 [PATCH] builtin/clean.c: Handle disappearing files David Turner
2015-05-14 21:45 ` Junio C Hamano
2015-05-14 21:52   ` David Turner
2015-05-14 22:14     ` Junio C Hamano
2015-05-14 22:33       ` David Turner
2015-05-15  5:26         ` Junio C Hamano
2015-05-15 18:13           ` David Turner
2015-05-16 19:21             ` Junio C Hamano [this message]

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=xmqqwq08e3bz.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dturner@twitter.com \
    --cc=dturner@twopensource.com \
    --cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.