public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygwin-3.1.0 and mintty from desktop shortcut
Date: Thu, 12 Mar 2020 20:46:01 +0100	[thread overview]
Message-ID: <878sk5tkzq.fsf@Rainer.invalid> (raw)
In-Reply-To: <20200312195731.2f8723a73ae0ae4d48fa9dbd@nifty.ne.jp> (Takashi Yano via Cygwin's message of "Thu, 12 Mar 2020 19:57:31 +0900")

Takashi Yano via Cygwin writes:
> Achim, can you build mintty locally? If so, could you please
> apply attahed patch to mintty 3.1.4 and report the output
> in mintty window?

I guess I can, but it will take time I don't have right now.  I'll see
what I can wedge in next week.

What I did figure out today is this:

The last working snapshot is the 2019-08-19 one, the next one
(2019-11-03) starts to fail already.  Unfortunately, between these two
snapshots most of the changes were put in.

Same as with your mintty
request I'll try to bisect the actual com,mit responsible, but I first
need to set up a build environment on another machione (SSD on my work
laptop is too full).  Again, unlikely to happen this or next week.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2020-03-12 19:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 23:26 [ANNOUNCEMENT] cygwin 3.1.0-1 Corinna Vinschen
2019-12-17  6:35 ` Thomas Wolff
2019-12-17  8:49   ` [GOLDSTAR][PLUSH HIPPO] " Corinna Vinschen
2019-12-17 20:58     ` Andrew Schulman via cygwin
2019-12-17 18:57 ` cygwin-3.1.0 and mintty from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.0-1) Achim Gratz
2019-12-18  9:07   ` Corinna Vinschen
2019-12-18 16:56     ` cygwin-3.1.0 and mintty from desktop shortcut Achim Gratz
2020-03-11 17:47       ` Achim Gratz
2020-03-11 19:51         ` Corinna Vinschen
2020-03-12  2:56           ` Rainer Emrich
2020-03-12 19:39             ` Achim Gratz
2020-03-12 21:36               ` Thomas Wolff
2020-03-13  1:03               ` Takashi Yano
2020-03-13  2:01                 ` Takashi Yano
2020-03-13 15:09                   ` Rainer Emrich
2020-03-13 21:26                   ` Achim Gratz
2020-03-13 22:20                     ` Ken Brown
2020-03-14 16:11                       ` Achim Gratz
2020-06-06 11:20                 ` ASSI
2020-06-07  1:35                   ` Takashi Yano
2020-06-07  5:29                     ` ASSI
2020-06-07  6:15                     ` Brian Inglis
2020-06-07  7:42                       ` Takashi Yano
2020-06-07  9:23                         ` Takashi Yano
2020-06-08  3:20                           ` Brian Inglis
2020-06-08 10:27                             ` Takashi Yano
2020-06-08 19:24                               ` Brian Inglis
2021-03-22 20:13                   ` Achim Gratz
2020-03-12 10:57           ` Takashi Yano
2020-03-12 19:46             ` Achim Gratz [this message]
2019-12-18 12:28   ` cygwin-3.1.0 and mintty from desktop shortcut (was: [ANNOUNCEMENT] cygwin 3.1.0-1) Takashi Yano
2019-12-18 17:17     ` cygwin-3.1.0 and mintty from desktop shortcut Achim Gratz
2019-12-18 10:18 ` [ANNOUNCEMENT] cygwin 3.1.0-1 Henning
2019-12-18 11:25   ` Corinna Vinschen
2019-12-20  9:40     ` Henning
2019-12-20 10:22       ` Corinna Vinschen
2019-12-20 16:20         ` Henning
2020-01-13 21:30   ` Houder
2020-01-14  0:20     ` Ken Brown

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=878sk5tkzq.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).