From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) by sourceware.org (Postfix) with ESMTPS id 30D1B3858413 for ; Sat, 2 Apr 2022 14:40:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 30D1B3858413 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id aZQinB3oMgTZYaevmnxW2Y; Sat, 02 Apr 2022 14:40:46 +0000 Received: from [10.0.0.5] ([184.64.124.72]) by cmsmtp with ESMTP id aevmnZFpB159UaevmnynIp; Sat, 02 Apr 2022 14:40:46 +0000 X-Authority-Analysis: v=2.4 cv=frTP2X0f c=1 sm=1 tr=0 ts=6248606e a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17 a=w_pzkKWiAAAA:8 a=8KDx8ZaCrbrJRTZ_:21 a=IkcTkHD0fZMA:10 a=JLfiFO2TdAYA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 a=daI9ojH3vpgA:10 a=9OEUv0ycuPhRH7phiczD:22 a=sRI3_1zDfAgwuvI8zelB:22 Message-ID: Date: Sat, 2 Apr 2022 08:40:46 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Reply-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 Content-Language: en-CA To: cygwin@cygwin.com References: <20220402063105.6E1DAA8098C@calimero.vinschen.de> From: Brian Inglis Organization: Systematic Software In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4xfONMrIEdGTKrnbC2VUp8rE4YFo3x+w1QUrUIpDBwK0KzyHvsWY9ohONSjSaI9B5neiysnThqIBbCo549Bfn3t/vrVpZYDtKk0La+4EeWEeIwgwOAOc+0 WQWPbjlls1370ePmtLJPMzPbs5pKRpMaZeBFQlf9lEMBXYo5VNnURPZWVj8s+LWerpnvOb4gBbHN6DYqNgceaE5631QYJKOmTZI= X-Spam-Status: No, score=-1163.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2022 14:40:48 -0000 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.]