From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: peflags warning and tsaware flags
Date: Fri, 27 Apr 2012 06:05:00 -0000 [thread overview]
Message-ID: <87ty054szm.fsf@Rainer.invalid> (raw)
In-Reply-To: <4F9A0DE4.7040008@cygwin.com>
Larry Hall (Cygwin) writes:
> Does this help?
Thanks, I've been reading this before. Tentatively I concluded that all
Cygwin executables should have the +tsaware set, I just wanted to make
sure that there aren't some that I would break if I do this.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
--
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:[~2012-04-27 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 15:16 Achim Gratz
2012-04-26 19:58 ` Corinna Vinschen
2012-04-26 20:28 ` Achim Gratz
2012-04-27 3:09 ` Larry Hall (Cygwin)
2012-04-27 6:05 ` Achim Gratz [this message]
2012-04-27 7:37 ` Corinna Vinschen
2012-04-27 8:55 ` Achim Gratz
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=87ty054szm.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).