-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Based on the number of reports to the main list about cygwin-1.5.19 interaction with bad samba inodes, and with find 4.2.27 reacting loudly while find 4.3.0 tends to do better (but not perfectly), I am considering bumping 4.3.0 to current. I'm also unsure why some people have claimed that oldfind 4.3.0 works when find 4.2.27 does not, since they use the same algorithm and compiled against the same cygwin version.
One benefit of making 4.3.0 current would be one less question to ask people when they report that "find isn't working" without attaching cygcheck output. On the other hand, 4.3.0 is marked alpha quality by the upstream maintainer (although I haven't encountered any serious problems with it). One other point: both 4.2.27-1 and 4.3.0-1 depend on cygwin 1.5.19, because they use getline(). To date, I have left 4.2.25-2 as the previous version since that way someone can use setup.exe to select cygwin 1.5.18 and an accompanying version of findutils that still works. If I made 4.3.0 current, should I leave 4.2.25 as previous, so that this scenario still works? Or should I bite the bullet and leave 4.2.27 as previous, so that people can still get the latest stable upstream version, but can no longer backrev findutils when they backrev cygwin? Or is 1.5.20 close enough on the horizon that I should just wait for it to come out? At that point I will probably release as current 4.3.0-2 that uses inodes (4.3.0-1 was compiled in the short window of time when d_ino did not exist), and would feel fine about leaving 4.2.27 as previous since cygwin 1.5.19 would be the oldest version that setup.exe would then support. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEO6J+84KuGfSFAYARAj+eAKDF58vFXhPWBjqw+QNi5CV/ULRdTQCgszXJ UKfQsgrISQ9A/mI1M/+9W1Q= =denU -----END PGP SIGNATURE-----
