public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Rich Eizenhoefer <riche@microsoft.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: From Microsoft: Windows 10 Console and Cygwin
Date: Mon, 01 Jun 2015 20:27:00 -0000	[thread overview]
Message-ID: <BN3PR03MB14303BAD46376DED807CFA2CB4B60@BN3PR03MB1430.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20150601082456.GG4308@calimero.vinschen.de>

This feature requires multiple moving parts from other teams at Microsoft and we have not started on it yet.  We have begun planning for the first post-Windows 10 release, and within our team we have talked about how to create hidden consoles and make the console driver/API better all around. I don't have a timeframe yet when we might get to this but it has been part of our presentation to management about the backlog items we prioritized. Overall there are almost 280 items on the backlog and  this is in the "elite 25" that are being considered.

Thanks,

Rich

-----Original Message-----
From: Corinna Vinschen [mailto:corinna-cygwin@cygwin.com] 
Sent: Monday, June 1, 2015 1:25 AM
To: cygwin@cygwin.com
Cc: Rich Eizenhoefer
Subject: Re: From Microsoft: Windows 10 Console and Cygwin

On May 31 11:51, Ismail Donmez wrote:
> Rich Eizenhoefer wrote
> > I've created a backlog item for this request so we can track the 
> > ask. It's possible, but would probably need to pick your brain 
> > in-depth more about the ask in the future. In the meantime, is it 
> > okay if I attach a copy of this email thread to the internal 
> > tracking item in our database? If not, I'll just keep the summary that I've already added.
> 
> I wonder if there is any news on this? Since Windows 10 RTM is 
> approaching it would be nice to have some update about this.

I'd sent my OK to attach the thread to Rich in PM during my vacation.


Corinna

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

  reply	other threads:[~2015-06-01 20:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 19:01 Rich Eizenhoefer
2015-04-29 19:50 ` Tim Prince
2015-04-29 20:06 ` Corinna Vinschen
2015-04-29 21:31   ` Rich Eizenhoefer
2015-04-30  8:22     ` Corinna Vinschen
2015-05-01 19:29       ` Rich Eizenhoefer
2015-05-02 13:47         ` Corinna Vinschen
2015-05-04 22:35           ` Rich Eizenhoefer
2015-05-05  8:22             ` Michael DePaulo
2015-05-31 20:07             ` Ismail Donmez
2015-06-01  8:24               ` Corinna Vinschen
2015-06-01 20:27                 ` Rich Eizenhoefer [this message]
2015-06-02  7:56                   ` Corinna Vinschen
2015-06-02  8:10                   ` İsmail Dönmez
2015-06-02 16:37                     ` Rich Eizenhoefer
2015-06-02 16:50                       ` Corinna Vinschen
2015-06-02 17:50                         ` Rich Eizenhoefer
2015-06-02 19:20                       ` Eric Blake
2015-06-02 20:36                         ` Vince Rice
2015-06-02 20:49                         ` Warren Young
2015-06-08 11:49                           ` Corinna Vinschen
2015-06-08 17:23                             ` Rich Eizenhoefer
2015-04-29 23:43   ` Michael DePaulo
2015-04-30  7:56     ` Corinna Vinschen
2015-04-30 11:27     ` LRN
2015-04-30 12:44       ` Tony Kelman

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=BN3PR03MB14303BAD46376DED807CFA2CB4B60@BN3PR03MB1430.namprd03.prod.outlook.com \
    --to=riche@microsoft.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).