From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Date: Sat, 2 Apr 2022 08:40:46 -0600 [thread overview]
Message-ID: <dea0d2a0-b317-0a66-ff57-5b0b2a87e2ff@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAKwdsS-mOrmd+Z0TN5g3whkaqUgBRrS_eO4B9d+L-YqcoX=hdw@mail.gmail.com>
On 2022-04-02 01:37, Backwoods BC wrote:
>> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
>
> I've only been on this list a few months, but I've seen these
> "find_fast_cwd" questions about twice a month so far.
>
> Might I suggest that replacing the
> "Please report this problem to the public mailing list cygwin@cygwin.com"
> message in 'bash' with something like:
> "Please visit https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
> for help with this issue"
This has been done in recent releases for some years, but ancient legacy
releases without changes are still distributed by/with some products or
projects, with no effort to upgrade what they distribute, mention of how
to upgrade, responsibility for or to their users.
Please read the linked FAQ entry for that explanation.
Ancient legacy repos such as SourceForge and GoogleCode are fertile
sources of such projects as are products from (some not so) defunct
embedded systems tool developers.
> This removes the need for an autoresponder and is more helpful at the
> same time. Users might be reluctant to join the mailing list just to
> report this and therefore they may waste their time needlessly trying
> to track down the problem.
That was why the autoresponder was added - reply directly to those folks
and point them to a greatly expanded FAQ entry with relevant links
explaining the problem and solution, and suggesting other actions.
I don't remember anyone clicking the email link at the end to let us
know what a product or project was or where it came from, so someone on
the list could follow up.
And folks wonder why there are software supply chain security issues!
--
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.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-04-02 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 6:28 James
2022-04-02 6:31 ` cygwinautoreply
2022-04-02 6:32 ` James
2022-04-02 7:37 ` Backwoods BC
2022-04-02 10:38 ` Eliot Moss
2022-04-02 14:40 ` Brian Inglis [this message]
2022-04-02 6:31 ` James
2022-04-04 7:29 ` Andrey Repin
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=dea0d2a0-b317-0a66-ff57-5b0b2a87e2ff@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).