From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Future setup regression caused by 'mkdir: always check-for-existence' commit
Date: Tue, 27 Aug 2019 17:54:00 -0000 [thread overview]
Message-ID: <877e6y7b24.fsf@Rainer.invalid> (raw)
In-Reply-To: <MWHPR21MB08455DEBE780ABD74CA7BFB5B9A10@MWHPR21MB0845.namprd21.prod.outlook.com> (Stephen Provine via cygwin's message of "Mon, 26 Aug 2019 22:13:19 +0000")
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, but the
bundled w/ GfW Msys2 here. There is no 3.0.7-3 Cygwin.
> All this said, Cygwin succeeds in both cases. And now that I look, I
> think the Cygwin setup program explicitly creates "/dev" as a standard
> directory so it avoids this change in behavior.
Yes, as I already wrote yesterday.
> Given that the new behavior is obviously correct, I assume this means
> there is nothing for Cygwin to do, and the fix is for Git for Windows
> to explicitly create this directory.
Preferrably, yes.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
--
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:[~2019-08-27 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:41 Stephen Provine via cygwin
2019-08-26 17:04 ` Eric Blake
2019-08-26 17:33 ` Ken Brown
2019-08-26 18:24 ` Stephen Provine via cygwin
2019-08-26 18:24 ` Ken Brown
[not found] ` <MWHPR21MB0845123AD4012BC4D100BE47B9A10@MWHPR21MB0845.namprd21.prod.outlook.com>
2019-08-27 12:51 ` Stephen Provine via cygwin
2019-08-27 17:54 ` Achim Gratz [this message]
2019-08-26 22:13 ` 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=877e6y7b24.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).