From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Рома <IceF1reX@i.ua>
Subject: Re: WARNING: Couldn't compute FAST_CWD pointer
Date: Fri, 02 Nov 2018 15:22:00 -0000 [thread overview]
Message-ID: <f32169cd-14ea-7e74-c10b-b3352f7ca0e5@SystematicSw.ab.ca> (raw)
In-Reply-To: <E1gIakK-0000Q0-JE@st13.mi6.kiev.ua>
On 2018-11-02 08:48, Рома wrote:
> I have error WARNING: Couldn't compute FAST_CWD pointer
This is just a warning to please upgrade Cygwin as explained at:
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
and please report the issue to whoever produces the software you are using.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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:[~2018-11-02 15:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 14:48 Рома
2018-11-02 15:21 ` Marco Atzeri
2018-11-02 15:22 ` Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 0:10 Lucas Rufino
2024-03-29 0:11 ` cygwinautoreply
2023-05-16 14:05 Mamadou BOBO DIALLO
2023-05-16 14:07 ` cygwinautoreply
2022-11-14 7:42 Fugro Weather
2022-11-14 7:45 ` cygwinautoreply
2021-03-09 14:57 Invertify
2021-03-09 15:13 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-07-13 9:26 Wissal Saihi
2020-07-13 9:29 ` cygwinautoreply
2020-05-30 14:46 =?gb18030?B?x+/M7LXEwOE=?=
2020-05-30 14:47 ` cygwinautoreply
2019-09-04 22:37 Jonathan Beit-Aharon
2019-09-04 22:39 ` cygwinautoreply
2019-04-16 1:04 Geno Chandler
2019-04-16 1:42 ` Jeffrey Walton
2019-04-16 5:01 ` cygwinautoreply
2018-10-24 14:32 Ng Wai Kin
2018-10-24 14:36 ` Stephen John Smoogen
2018-10-24 14:41 ` john doe
2018-10-24 14:57 ` cyg Simple
2018-09-21 17:18 Elizabeth Carter
2018-09-21 17:28 ` Marco Atzeri
2018-09-03 5:42 Christine dbit
2018-09-03 7:07 ` Marco Atzeri
2018-08-07 12:52 sepide sarajian
2018-08-07 13:49 ` Marco Atzeri
2018-08-06 0:01 Anietie Essiet
2018-08-06 7:52 ` Csaba Raduly
2018-07-11 5:19 Aghil Vinayak
2018-07-11 7:00 ` David Billinghurst
2016-07-08 5:21 Martin Gregory
2016-07-08 6:03 ` Marco Atzeri
2014-09-09 18:34 Eric Lu
2014-09-09 18:37 ` Douglas Coup
2014-09-11 0:07 ` Yaakov Selkowitz
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=f32169cd-14ea-7e74-c10b-b3352f7ca0e5@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=IceF1reX@i.ua \
--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).