From: "Walter L." <bournenoir@hotmail.com>
To: <cygwin@cygwin.com>
Subject: Re: Issues encountered with new Cygwin version
Date: Fri, 25 Sep 2015 18:01:00 -0000 [thread overview]
Message-ID: <BLU182-DS3FA926E18C37A612F5D99D4420@phx.gbl> (raw)
In-Reply-To: <56057078.3080907@cornell.edu>
On 9/25/2015 12:04 PM, Ken Brown wrote:
> > I think you misunderstood what Marco was saying. If the problem is
> > caused by the default ACL on the directory, you could fix that ACL.
>
> To elaborate on this, observe the following:
Hi Ken, thanks for the clarification. I understood what Marco meant and your
examples. I was just saying that the new (correct?) behavior of inheriting
the ACL from the parent folder for newly created file has the side effect of
causing Git to behave differently from before.
I suppose the point you're making (based on your example) is that I should
just remove the ACL from the parent folder if I don't want new files in the
folder to inherit the executable bit. If that's the case then I guess I'll
need to do that anytime I clone a new project.
Regards,
~WL
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-09-25 18:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 23:04 Walter L.
2015-09-23 8:20 ` Andrey Repin
2015-09-23 14:47 ` Walter L.
2015-09-23 16:20 ` Andrey Repin
2015-09-24 2:39 ` Linda Walsh
2015-09-24 4:34 ` Walter L.
2015-09-24 4:43 ` Linda Walsh
2015-09-24 10:35 ` Andrey Repin
2015-09-24 13:21 ` Walter L.
2015-09-24 16:49 ` Linda Walsh
2015-09-24 18:35 ` Andrey Repin
2015-09-25 15:01 ` Walter L.
2015-09-25 15:23 ` Ken Brown
2015-09-25 16:04 ` Ken Brown
2015-09-25 18:01 ` Walter L. [this message]
2015-09-25 18:24 ` Ken Brown
2015-09-25 18:37 ` Walter L.
2015-09-26 9:21 ` Andrey Repin
2015-09-26 20:26 ` Walter L.
2015-09-26 22:10 ` Ken Brown
2015-09-27 3:56 ` Walter L.
2015-09-27 10:05 ` Andrey Repin
2015-09-27 14:45 ` Walter L.
2015-09-24 2:26 ` Linda Walsh
2015-09-24 5:35 ` Marco Atzeri
2015-09-24 14:24 ` base-files-4.2-3 : attention maintainer Marco Atzeri
2015-09-24 17:29 ` Achim Gratz
2015-09-25 18:53 ` Ken Brown
2015-09-26 9:21 ` Andrey Repin
2015-09-26 9:57 ` Achim Gratz
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=BLU182-DS3FA926E18C37A612F5D99D4420@phx.gbl \
--to=bournenoir@hotmail.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).