From: Vince Rice <vrice@solidrocksystems.com>
To: L A Walsh <cygwin@tlinx.org>
Cc: cygwin@cygwin.com
Subject: Re: Getting error message when launching X-Window apps in Cygwin
Date: Sat, 09 Feb 2019 19:06:00 -0000 [thread overview]
Message-ID: <B5785D2B-EAD8-4B14-BF2E-3999885318E7@solidrocksystems.com> (raw)
In-Reply-To: <5C5EE7D2.2010404@tlinx.org>
> On Feb 9, 2019, at 8:46 AM, L A Walsh <cygwin@tlinx.org> wrote:
>
> …
>
> For me, …
What you think about this is irrelevant. What I think about this is
irrelevant. The only thoughts that matter are the ones of those who
manage the list, and they have said this is a "do not top post" list.
Others who say "do not top post here" aren't (necessarily) arguing
about which is better, they are stating list policy. Arguing with them
is pointless, because they didn't set the policy.
This list is a "do not top post" list. If you want to post here, then don't
top post.
--
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:[~2019-02-09 19:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308285295.576965.1549657291745.ref@mail.yahoo.com>
2019-02-08 20:21 ` akshay chavan via cygwin
2019-02-09 6:27 ` akshay chavan via cygwin
2019-02-09 13:50 ` Andrey Repin
2019-02-09 14:46 ` L A Walsh
2019-02-09 16:34 ` Posting etiquette: Was: " Jack
2019-02-09 18:26 ` Posting Order (was: Getting error message...) Brian Inglis
2019-02-09 23:02 ` bzs
2019-02-10 0:36 ` Posting Order L A Walsh
2019-02-10 0:36 ` L A Walsh
2019-02-10 6:13 ` Brian Inglis
2019-02-09 19:06 ` Vince Rice [this message]
2019-02-10 0:02 ` Getting error message when launching X-Window apps in Cygwin L A Walsh
2019-02-10 0:43 ` Vince Rice
2019-02-10 8:43 ` Corinna Vinschen
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=B5785D2B-EAD8-4B14-BF2E-3999885318E7@solidrocksystems.com \
--to=vrice@solidrocksystems.com \
--cc=cygwin@cygwin.com \
--cc=cygwin@tlinx.org \
/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).