From: Reese Borchers <rborchers@optimation.com>
To: cygwin@cygwin.com
Subject: FAST_CWD pointer
Date: Wed, 31 Aug 2022 10:16:23 -0500 [thread overview]
Message-ID: <CAHdQ3CWUHLen8Aat_gFT04E3RmExvaPLaqnut9aiNi-Y2x-CNw@mail.gmail.com> (raw)
Cygwin,
I have a customer of ours that uses cygwin and they started getting this
error. We have not seen this before. Is there anything we can do to fix
this?
5[main] mv 520 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer:
Please report this problem to the public mailing list cygwin@cygwin.com
Thank you,
--
*Reese Borchers*
Manufacturing Services Support, *Optimation*
700 NE RD Mize Rd. Suite 101, Blue Springs, MO, 64014
*(816)509-9974 rborchers@optimaiton.com <rborchers@optimaiton.com>*
WARNING: multiple messages have this Message-ID
From: Reese Borchers <rborchers@optimation.com>
To: cygwin@cygwin.com
Subject: FAST_CWD pointer
Date: Wed, 31 Aug 2022 10:16:23 -0500 [thread overview]
Message-ID: <CAHdQ3CWUHLen8Aat_gFT04E3RmExvaPLaqnut9aiNi-Y2x-CNw@mail.gmail.com> (raw)
Message-ID: <20220831151623.vYCRWJdGdsygLQoK3UUqAqnHtJii2J7I5ANQ_Z2HEi0@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
Cygwin,
I have a customer of ours that uses cygwin and they started getting this
error. We have not seen this before. Is there anything we can do to fix
this?
5[main] mv 520 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer:
Please report this problem to the public mailing list cygwin@cygwin.com
Thank you,
--
*Reese Borchers*
Manufacturing Services Support, *Optimation*
700 NE RD Mize Rd. Suite 101, Blue Springs, MO, 64014
*(816)509-9974 rborchers@optimaiton.com <rborchers@optimaiton.com>*
next reply other threads:[~2022-08-31 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 15:16 Reese Borchers [this message]
2022-08-31 15:16 ` Reese Borchers
2022-08-31 15:17 ` cygwinautoreply
-- strict thread matches above, loose matches on Subject: below --
2021-03-31 19:19 Dale Kendall
2021-03-31 19:21 ` cygwinautoreply
2015-12-15 8:15 Hugo Leisink
2015-12-15 8:35 ` 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=CAHdQ3CWUHLen8Aat_gFT04E3RmExvaPLaqnut9aiNi-Y2x-CNw@mail.gmail.com \
--to=rborchers@optimation.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).