public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vince Rice <vrice@solidrocksystems.com>
To: cygwin@cygwin.com
Subject: Re: urgent help for tool
Date: Mon, 22 Oct 2018 22:37:00 -0000	[thread overview]
Message-ID: <FCAEDDDD-DBF3-4F46-91C2-87A58A04842A@solidrocksystems.com> (raw)
In-Reply-To: <d1980d70-2eb5-e133-d884-a5768ea4095a@towo.net>

> On Oct 22, 2018, at 5:27 PM, Thomas Wolff wrote:
> 
> Lots of people wrote:
>>>>> 1 [main] bash 9316 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.
>>>>> Please report this problem to
>>>>> the public mailing list cygwin@cygwin.com
>>>>> ...
>>>>> 
>>>> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
> Can we change that error hint so that it points to a suitable help page rather than the mailing list which is getting spammed by lots of people who don't even have an idea how to put a meaningful title on their report?

Already been done (well, something similar). Read the FAQ entry.

It doesn't help for the old versions of cygwin that are being reported. That's why they're getting that message—because it's an old version.
They're not spamming, they're doing exactly what the message told them to do. The message was unfortunate from the get-go.

Now that has come up yet again, I do wonder if the mailing list software could somehow trap an unquoted FAST_CWD message and just reply with a message that includes a link to the FAQ entry, rather than send the message onto the list. Probably more trouble than it's worth.




--
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

  reply	other threads:[~2018-10-22 22:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <126044976.64091860.1540220616710.JavaMail.zimbra@u-psud.fr>
2018-10-22 15:05 ` Samir Bouaziz
2018-10-22 15:10   ` john doe
2018-10-22 17:49     ` Marco Atzeri
2018-10-22 21:14       ` Brian Inglis
2018-10-22 22:27         ` Thomas Wolff
2018-10-22 22:37           ` Vince Rice [this message]
2018-10-23  7:57             ` Corinna Vinschen
2018-10-24 14:39               ` Stefan Baur
2018-10-24 20:50                 ` Andrey Repin
2018-10-24 21:06                   ` Hans-Bernhard Bröker
2018-10-24 21:44                     ` Vince Rice

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=FCAEDDDD-DBF3-4F46-91C2-87A58A04842A@solidrocksystems.com \
    --to=vrice@solidrocksystems.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).