From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Please report this problem to the public mailing list...
Date: Tue, 24 Jan 2017 15:33:00 -0000 [thread overview]
Message-ID: <d4ddcab5-c10a-79a4-f0d2-538411ee6d00@gmail.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A704BBDC825@USA7109MB022.na.xerox.net>
On 1/24/2017 10:21 AM, Nellis, Kenneth (Conduent) wrote:
> We have received several postings of people responding to the Cygwin-generated
> message: WARNING: ... Please report this problem to the public mailing list
> cygwin@cygwin.com.
>
> I wonder how many places such messages are present in the Cygwin code.
>
> Just throwing out an idea here to help people help themselves...
>
> Consider all such messages carrying an error code and referred to a Cygwin web
> page that contained links to separate pages for each error code, and those pages,
> then, would contain the latest information as to how to recover from the
> respective errors.
>
Great idea. I can see this
> Problem reports: http://cygwin.com/problems.html
being referenced instead of the mail list which the person may not be
subscribed to. Care to present a patch to the web page? And we need a
patch to the text parts of Cygwin to point to the web page.
--
cyg Simple
--
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
next prev parent reply other threads:[~2017-01-24 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 15:22 Nellis, Kenneth (Conduent)
2017-01-24 15:33 ` cyg Simple [this message]
2017-01-24 19:51 ` Corinna Vinschen
2017-01-24 19:53 ` Corinna Vinschen
2017-01-24 20:27 ` Brian Inglis
2017-01-25 20:27 ` cyg Simple
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=d4ddcab5-c10a-79a4-f0d2-538411ee6d00@gmail.com \
--to=cygsimple@gmail.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).