From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>, anessiet@gmail.com
Subject: Re: WARNING: Couldn't compute FAST_CWD pointer.
Date: Mon, 06 Aug 2018 07:52:00 -0000 [thread overview]
Message-ID: <CAEhDDbAa-JVKP=E_0cKidPuznsYxQvU+j=j6=-y8bdgGe7yLWA@mail.gmail.com> (raw)
In-Reply-To: <CAEorQfUsA7WUJeCroE=XzLpk=zKQK2ZQHeVx7uyN95Q06THnLQ@mail.gmail.com>
Hi,
On Mon, Aug 6, 2018 at 2:01 AM, Anietie Essiet wrote:
> Hello
>
> I tried to edit a code file on SIM to be able to run a new algorithm,
> however I am getting the above subject warning. How do I correct this
> please?
>
https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
--
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-08-06 7:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 0:01 Anietie Essiet
2018-08-06 7:52 ` Csaba Raduly [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-11-02 14:48 Рома
2018-11-02 15:21 ` Marco Atzeri
2018-11-02 15:22 ` Brian Inglis
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-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='CAEhDDbAa-JVKP=E_0cKidPuznsYxQvU+j=j6=-y8bdgGe7yLWA@mail.gmail.com' \
--to=rcsaba@gmail.com \
--cc=anessiet@gmail.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).