From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 3.1.6
Date: Tue, 26 May 2020 14:36:24 -0600 [thread overview]
Message-ID: <4ea077c6-c7dc-699f-dc0e-ee8bee421819@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAHvU03X=rHkZPE1rEmO1HAF4WKmw=s+zC+f1RNgNVu5CzcPaow@mail.gmail.com>
On 2020-05-26 13:16, Maarten Hoes via Cygwin wrote:
> On Tue, May 26, 2020 at 7:36 PM Thomas Wolff wrote:
>> and please remember not to "top-post" if you respond there]
> [not aimed at you specifically, but ]
> Owwwh, for the love of ***, can 'we' be at least a little more lenient
> about this? I fully realize that people have their clear preferences here,
> but [like the 'indent by spaces or tabs' discussion]:
> The eighties called, and they want they're discussion back.
[Please trim email addresses from bodies so they do not appear in archives!]
Outlook TOFU email posting style is manageable for a one-on-one personal email
thread, but it's a mess when you have posters providing minimal information in
each response to requests for more info, from multiple volunteer respondents who
would like to understand enough to help, or multiple subthreads with followups
in different directions.
Some maintainers are extremely busy with limited time to either respond here, or
upgrade or diagnose and fix problems with packages, so just won't respond to
TOFU, posters who provide insufficient information, or think there is a company
or employees providing Cygwin products and support, rather than all being
volunteers, and who expect or demand immediate "mystical" support in response to
a message like "something broke and we think it might be Cygwin".
Others here will try to pry enough information from posters to point them in a
useful direction, or provide enough comprehensible information in a format that
busy maintainers can quickly read and address an issue with a package.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-05-26 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 17:41 Thomas Wolff
2020-05-22 9:22 ` Takashi Yano
2020-05-22 10:14 ` Thomas Wolff
2020-05-22 11:01 ` Takashi Yano
2020-05-22 12:58 ` Takashi Yano
2020-05-22 13:54 ` Takashi Yano
2020-05-22 14:56 ` Takashi Yano
2020-05-22 20:16 ` Thomas Wolff
2020-05-26 14:30 ` David Dombrowsky
2020-05-26 14:49 ` Thomas Wolff
2020-05-26 15:15 ` Randall Nutz
2020-05-26 15:31 ` Thomas Wolff
[not found] ` <CAMVJNJuDbQ=Y5qCy=C8rUSaqnA+MXszrJqbAWdyM5YFfAK7Wdw@mail.gmail.com>
2020-05-26 17:14 ` Thomas Wolff
2020-05-26 19:16 ` Maarten Hoes
2020-05-26 19:53 ` Marco Atzeri
2020-05-26 20:18 ` Maarten Hoes
2020-05-26 20:36 ` Brian Inglis [this message]
2020-05-26 21:00 ` Maarten Hoes
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=4ea077c6-c7dc-699f-dc0e-ee8bee421819@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).