public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Andy Koppe <andy.koppe@gmail.com>
Subject: Re: mintty project
Date: Mon, 01 Jun 2015 16:33:00 -0000	[thread overview]
Message-ID: <20150601163329.GQ4308@calimero.vinschen.de> (raw)
In-Reply-To: <87pp5fl827.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

On Jun  1 18:14, Achim Gratz wrote:
> Thomas Wolff writes:
> > I'd like to discuss what you (cygwin maintainers and others) think of
> > this move, whether it's good for mintty to be hosted on
> > github.
> 
> The first thing should really be to find out what Andy Koppe thinks
> about this, or is there any information about his whereabouts that says
> he's abandoned his project (other than the long silence)?

Well, I don't know what Andy really wants.  I pinged him May 2015 and he
replied a couple of days later.  Life was taking a toll, so he was not
actively working on mintty anymore.  He told me he'd have a look into
providing a new mintty version.  I pinged him twice since then, once in
October 2014, once in January 2015.  I'm willing to ping Andy again
(done with this mail), but if he doesn't reply we should really go
forward I think, even if it's unfortunate, Andy being a nice guy.

> And that question of yours is moot since mintty already is on GitHub, in
> 26 different forks.  Most of them are "Automatically exported from
> Google Code." and some not even fully up-to-date.  Then closest to
> Cygwin is the one from cygwinports (Yaakov).

That should probably be the version going ahead with...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-01 16:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 21:49 Thomas Wolff
2015-06-01  7:03 ` Tony Kelman
2015-06-01  8:36 ` Corinna Vinschen
2015-06-01 14:16   ` Frank Fesevur
2015-06-01 15:50     ` Corinna Vinschen
2015-06-05  5:36       ` Thomas Wolff
2015-06-08 12:13         ` Corinna Vinschen
2015-06-08 20:11           ` Csaba Raduly
2015-06-09  9:57             ` Corinna Vinschen
2015-06-09 19:55               ` Thomas Wolff
2015-06-10  8:18                 ` Corinna Vinschen
2015-06-23 18:54         ` Corinna Vinschen
2015-06-02  6:05   ` Thomas Wolff
2015-06-02  7:59     ` Corinna Vinschen
2015-06-01 16:14 ` Achim Gratz
2015-06-01 16:33   ` Corinna Vinschen [this message]
2015-06-02 18:04     ` Thomas Wolff
2015-06-02 18:39       ` Tony Kelman
2015-06-04  6:29         ` Thomas Wolff
2015-06-04  8:16           ` Frank Fesevur
2015-06-01 16:55   ` Eric Blake

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=20150601163329.GQ4308@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=andy.koppe@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).