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: Wed, 24 Oct 2018 21:44:00 -0000	[thread overview]
Message-ID: <3D531107-55FE-49ED-9501-783A4B9A1A82@solidrocksystems.com> (raw)
In-Reply-To: <aff9267b-e5ce-497f-a9f3-8662198ac7d3@t-online.de>

> On Oct 24, 2018, at 4:05 PM, Hans-Bernhard Bröker wrote:
> 
> A less disruptive approach would be just a) switch this list from
> anybody-can-post to subscribers-only, at least for the time being, and
> then b) put the FAQ pointers about FAST_CWD prominently into the
> auto-reply for non-subscribed users.  At the very least this would have
> the benefit of not breaking the continuity of the mailing list archives.

An even less disruptive approach would be to just auto-reply to the original
FAST_CWD message, which is what Corinna has already indicated in this
thread that she look into as she has time.
--
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-24 21:44 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
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 [this message]

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=3D531107-55FE-49ED-9501-783A4B9A1A82@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).