public inbox for
 help / color / mirror / Atom feed
From: Andy Koppe <>
To: The Vulgar and Unprofessional Cygwin-Talk List <>
Subject: Re: default terminal (was: Re: "can't create master tty" errors)
Date: Tue, 01 Jun 2010 11:45:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 1 June 2010 09:20, Corinna Vinschen wrote:
> On May 31 20:42, Christopher Faylor wrote:
>> On Mon, May 31, 2010 at 11:34:37PM +0100, Andy Koppe wrote:
>> >On 31 May 2010 22:29, Christopher Faylor:
>> >> Part of the reason I want to do this is that I just saw Andy commenting
>> >> in a "Death of Cygwin" blog post where the author was surprised that
>> >> something like mintty existed at all.
>> >
>> >Seems the author has quietly retracted his post, including our
>> >comments. How classy.
>> Classy, indeed.  I mean to go back and see if there was a response to my
>> response.  I guess that was it.
> Any chance to find a copy of the blog via the google memory?  What was
> the name of the blog and where was it?

"It's Time for Cygwin to Close Shop", at Still appears on Google, but the
cached copy there doesn't work. I found it in my browser's cache
though. Says it's under a Creative Commons license, so attaching it
here is fine I hope.


  parent reply	other threads:[~2010-06-01 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2010-05-31 22:34   ` Andy Koppe
2010-06-01  0:42     ` Christopher Faylor
2010-06-01  8:20       ` Corinna Vinschen
2010-06-01 11:00         ` Mike Marchywka
2010-06-01 11:45         ` Andy Koppe [this message]
2010-06-01 14:14           ` Christopher Faylor
     [not found]             ` <>
2010-06-01 17:28               ` Christopher Faylor
2010-06-01 18:01                 ` Andy Koppe
2010-06-01 18:55                 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).