From: Robert McBroom <mcforum@bellsouth.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.8.4 {GOLDSTAR]
Date: Tue, 06 Feb 2018 05:48:00 -0000 [thread overview]
Message-ID: <5ff03e5b-5745-4e36-bc5e-fb24f7bd0d75@bellsouth.net> (raw)
In-Reply-To: <79f1d568-aca8-05c8-cb29-80d917755745@SystematicSw.ab.ca>
On 02/06/2018 12:35 AM, Brian Inglis wrote:
> On 2018-02-05 21:45, Yaakov Selkowitz wrote:
>> On 2018-02-05 20:01, Andrew Schulman wrote:
>>>> I have uploaded mintty 2.8.4 with the following changes:
>>> I'll just take this opportunity to say thanks for maintaining this really
>>> central application in Cygwin. I use it every day to get my work done. Andrew
>> Then let's do something about it. :-D
> He should be severely castigated for his prescient behaviour of adding new
> features and fixing problems before we can report them. Should we pin an old
> guy's Gold Watch on him, give him five Golden Rings^WStars so long after Xmas,
> or do his mintty actions deserve the most extreme treatment, [Oh, no! *NOT*...]
> the (Pink) Plush Hippo?
>
AVG ANTIVIRUS on Win 7 thinks mintty is a virus after update. Shame on them.
--
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:[~2018-02-06 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 23:53 [ANNOUNCEMENT] Updated: mintty 2.8.4 Thomas Wolff
2018-02-06 2:02 ` Andrew Schulman
2018-02-06 4:45 ` [ANNOUNCEMENT] Updated: mintty 2.8.4 {GOLDSTAR] Yaakov Selkowitz
2018-02-06 5:35 ` Brian Inglis
2018-02-06 5:48 ` Robert McBroom [this message]
2018-02-06 15:45 ` Andrew Schulman
2018-02-06 20:44 ` Thomas Wolff
2018-02-06 5:51 ` [ANNOUNCEMENT] Updated: mintty 2.8.4 Jim Garrison via cygwin
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=5ff03e5b-5745-4e36-bc5e-fb24f7bd0d75@bellsouth.net \
--to=mcforum@bellsouth.net \
--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).