-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Dave Korn on 1/18/2009 2:42 PM: > However, you may have to recreate all the cygwin-specific patches that the > cygwin bash maintainer hasn't managed to send upstream yet...
Not only that, but some of those patches will never be sent upstream, because they are too platform-specific. As for this particular issue of freopen, I'm dragging my feet - the cygwin patch works, and no other mainstream platform is affected, so even though I have _already_ pointed out upstream that the current freopen use is buggy, I haven't bothered patching things upstream yet (I only have so much free time). http://lists.gnu.org/archive/html/bug-coreutils/2008-10/msg00199.html >> However, I noticed there are some very weird bugs happening. See for >> example, this bug in cat (don't look at the title of the page, I blamed >> bash first) >> http://paster.dazjorz.com/?p=3845 Yes, this is a known upstream bug in coreutils, but which only affects cygwin, and which is already fixed on cygwin, so there is very little need or desire to spend time fixing it upstream. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklzrW4ACgkQ84KuGfSFAYBiMwCcCmf54S2kJPf8e/cO79NVVkFi Xz0AoKBlI79e4GNO/wLOHK7fv9PhOYec =PekT -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/