public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Kaz Kylheku (Cygwin)" <743-406-3965@kylheku.com>
To: cygwin@cygwin.com
Subject: Re: Warning cygwin
Date: Mon, 22 Feb 2021 16:59:19 -0800	[thread overview]
Message-ID: <3bc30b4db1a11e86f17ca6a236bcb440@mail.kylheku.com> (raw)
In-Reply-To: <b5a89b66-ab32-4b7c-3ed2-384a8d332bbf@SystematicSw.ab.ca>

On 2021-02-22 15:53, Brian Inglis wrote:
> On 2021-02-22 16:41, Kaz Kylheku wrote:
>> On 2021-02-22 11:19, cygwinautoreply wrote:
>>> https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
>> 
>> It would be ideal if this auto-reply didn't include the Cygwin
>> mailing list; there is no need for the mailing list to read this.
>> 
>> Scratch that; it would be ideal if neither the original question
>> nor the auto-reply were re-mailed.
> 
> What if Cygwin is up to date and you see that message?

Right.

In that case, the message from newer Cygwin will not be accompanied
by a recommendation to post to the mailing list. Instead it points
to some online resources about the problem.

Those resources could loudly warn the user that mailing list messages
containing references to the FAST_CWD will receive a robot reply
and not get posted (for he reason that old releases of Cygwin
encouraged users to post reports of it, which keeps happening).



  reply	other threads:[~2021-02-23  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 19:18 knut.franzke.kf
2021-02-22 19:19 ` cygwinautoreply
2021-02-22 23:41   ` Kaz Kylheku (Cygwin)
2021-02-22 23:53     ` Brian Inglis
2021-02-23  0:59       ` Kaz Kylheku (Cygwin) [this message]
2021-02-23  9:13         ` Brian Inglis

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=3bc30b4db1a11e86f17ca6a236bcb440@mail.kylheku.com \
    --to=743-406-3965@kylheku.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).