when running commands like pull and clone I get the following message:
Cygwin WARNING:
Couldn't compute FAST_CWD pointer. This typically occurs if you're using
an older Cygwin version on a newer Windows. Please update to the latest
available Cygwin version from https://cygwin.com/. If the problem
persists,
please see https://cygwin.com/problems.html
Windows build is version 1607, OS BUILD 15002.1001
I assume they broke something that cygwin was depending on.
Hi Michael,
On Thu, 12 Jan 2017, Michael Gooch wrote:
when running commands like pull and clone I get the following message:
Cygwin WARNING:
Couldn't compute FAST_CWD pointer. This typically occurs if you're using
an older Cygwin version on a newer Windows. Please update to the latest
available Cygwin version from https://cygwin.com/. If the problem
persists,
please see https://cygwin.com/problems.html
Windows build is version 1607, OS BUILD 15002.1001
I assume they broke something that cygwin was depending on.
This is not only a known problem, we already have a fix for it, too.
Please note that the recommended way [*1*] to report bugs in Git for
Windows would have led you to this ticket:
https://github.com/git-for-windows/git/issues/1029
Please also note that this is only a warning, not an error. Even so, the
problem has been reported independently several times...
There have been enough real fixes have been accumulated in Git for
Windows' `master` branch, and the next official Git version is far enough
in the future [*2*] that it was time for a Git for Windows version,
including the fix for the FAST_CWD warning.
Ciao,
Johannes
Footnote *1*: https://git-for-windows.github.io/#contribute
Footnote *2*: http://tinyurl.com/gitCal suggests that Git v2.12.0 will be
released early February soon after Git Merge (and Git for Windows v2.12.0
will follow soon thereafter), and with no patches applied to the `maint`
branch since v2.11.0, I do actually not expect any v2.11.1 to happen
before v2.12.0 comes out.
Hi,
On Sat, 14 Jan 2017, Johannes Schindelin wrote:
Footnote *2*: http://tinyurl.com/gitCal suggests that Git v2.12.0 will
be released early February soon after Git Merge (and Git for Windows
v2.12.0 will follow soon thereafter), and with no patches applied to the
`maint` branch since v2.11.0, I do actually not expect any v2.11.1 to
happen before v2.12.0 comes out.
And just to prove me wrong, today I got the first update to `maint` in six
weeks, with a message "Almost ready for 2.11.1" at its tip, featuring a
whopping 141 commits (95 of which are not merge commits).
So it seems that v2.11.1 may happen soon, after all.
Sorry for my misjudgement,
Johannes