From: Jeff King <peff@peff.net>
To: Computer Druid <computerdruid@gmail.com>
Cc: Chad Joan <chadjoan@gmail.com>, git@vger.kernel.org
Subject: Re: Git changes permissions on directories when deleting files.
Date: Tue, 1 Mar 2011 15:57:02 -0500 [thread overview]
Message-ID: <20110301205702.GA21429@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTinkjhH6YR7VPC0hji9CK=qeQMAYr+ptJE3szUyR@mail.gmail.com>
On Tue, Mar 01, 2011 at 03:39:10PM -0500, Computer Druid wrote:
> > I'll do that, but it will probably take a long long time for me to see
> > the patch. I'm hoping there's some cheap hack I can use to work
> > around it in the meantime.
>
> A simple answer to preventing git from calling rmdir would be to run
> rm and git rm separately:
> $ rm file
> $ git rm --cached -f file
>
> But that doesn't solve the misbehavior of git under the previous
> scenario. I'm not sure if this is something we should fix in git or if
> it should be fixed in cifs.
That will fix some instances. But git will rmdir to clean up anytime it
removes content. That includes during a merge or patch application. So
you can't really get around those cases.
-Peff
next prev parent reply other threads:[~2011-03-01 20:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 1:42 Git changes permissions on directories when deleting files Chad Joan
2011-03-01 1:45 ` Chad Joan
2011-03-01 2:19 ` Computer Druid
2011-03-01 4:00 ` Chad Joan
2011-03-01 15:51 ` Chad Joan
2011-03-01 17:11 ` Computer Druid
2011-03-01 19:35 ` Chad Joan
2011-03-01 19:44 ` Jeff King
2011-03-01 19:57 ` Chad Joan
2011-03-01 20:08 ` Jeff King
2011-03-01 20:30 ` Chad Joan
2011-03-01 20:39 ` Computer Druid
2011-03-01 20:57 ` Jeff King [this message]
2011-03-01 20:43 ` Matthieu Moy
2011-03-01 20:46 ` Chad Joan
2011-03-01 21:08 ` Jeff King
2011-03-03 3:48 ` Chad Joan
2011-03-03 15:16 ` Jeff King
2011-03-11 6:09 ` Chad Joan
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=20110301205702.GA21429@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=chadjoan@gmail.com \
--cc=computerdruid@gmail.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.