Re: Future setup regression caused by 'mkdir: always check-for-existence' commit

Stephen Provine via cygwin writes: > I should also point out that this change in behavior starts not in > 3.1.0 but in 3.0.7-3, and in-between 3.0.7-1 and 3.0.7-3 the commit I > mention seemed like the most reasonable reason for it. You should also point out that you are talking not about Cygwin,

RE: Future setup regression caused by 'mkdir: always check-for-existence' commit

On 8/26/2019 1:33 PM, Ken Brown wrote: > I don't think you understand the logic change in that commit. An attempt to > create an existing directory would already fail before that commit; the > failure would occur in the call to fh->mkdir(). The commit in question > simply guarantees that the e

Re: Future setup regression caused by 'mkdir: always check-for-existence' commit

Stephen Provine via cygwin writes: > After this change (commit b0c033bf3fae810b9e5a5c69f17bd4de63725691), > the Git for Windows setup (and future Cygwin setups) do not correctly > configure bash features because the post-install step for configuring > the /dev directory does not work any more. Cyg

Re: Future setup regression caused by 'mkdir: always check-for-existence' commit

[Please don't top-post on this list. Thanks.] On 8/26/2019 1:33 PM, Stephen Provine via cygwin wrote: > It's possible that this issue contributes to the problem, but the fact that > you can manually create the "dev" directory outside of Cygwin (just mkdir > from Windows command prompt) to fix t

RE: Future setup regression caused by 'mkdir: always check-for-existence' commit

be created in the first place. I'd be happy to try the test release for cygwin-3.1.0, but I don't know how to find it. Can you provide a link? Thanks, Stephen -Original Message- From: Ken Brown Sent: Monday, August 26, 2019 10:04 AM To: cygwin@cygwin.com Cc: Stephen Provine Su

Re: Future setup regression caused by 'mkdir: always check-for-existence' commit

On 8/26/2019 11:25 AM, Stephen Provine via cygwin wrote: > After this change (commit b0c033bf3fae810b9e5a5c69f17bd4de63725691), the Git > for Windows setup (and future Cygwin setups) do not correctly configure bash > features because the post-install step for configuring the /dev directory > doe

Re: Future setup regression caused by 'mkdir: always check-for-existence' commit

On 8/26/19 10:25 AM, Stephen Provine via cygwin wrote: > After this change (commit b0c033bf3fae810b9e5a5c69f17bd4de63725691), the Git > for Windows setup (and future Cygwin setups) do not correctly configure bash > features because the post-install step for configuring the /dev directory > does

Future setup regression caused by 'mkdir: always check-for-existence' commit

After this change (commit b0c033bf3fae810b9e5a5c69f17bd4de63725691), the Git for Windows setup (and future Cygwin setups) do not correctly configure bash features because the post-install step for configuring the /dev directory does not work any more. It used to be that "mkdir -m 755 /dev" would