[bug #30504] bug/rfe....the "-P" option seems to be unusable by itself

Follow-up Comment #6, bug #30504 (project findutils): The mailing list address is given in the BUGS section of the manpage: The best way to report a bug is to use the form at http://savannah.gnu.org/bugs/?group=findutils. The reason for this is that you will then be able to track pro

[bug #30103] find -name \* doesn't match for (some) special chars (especially chinese)

Update of bug #30103 (project findutils): Status:None => Duplicate Assigned to:None => jay Open/Closed:Open => Closed Summary

[bug #29949] find -execdir does not change working directory

Update of bug #29949 (project findutils): Summary: find -execdr does not change working directory => find -execdir does not change working directory ___ Reply to this item at: ___

[bug #26701] if there are any funny characters, * no longer matches in certain locales

Update of bug #26701 (project findutils): Status:None => Confirmed ___ Reply to this item at: ___

[bug #19969] rc-125.exp fails on some systems

Follow-up Comment #5, bug #19969 (project findutils): Is it possible that you could retest this, please? ___ Reply to this item at: ___ Message sent vi

[bug #19973] Setup for samefile-p-brokenlink.exp fails

Follow-up Comment #6, bug #19973 (project findutils): Nelson, any news? ___ Reply to this item at: ___ Message sent via/by Savannah http://savannah.g

[bug #22301] find fails on Solaris automount points when configured --with-fts

Update of bug #22301 (project findutils): Status: Need Info => Wont Fix Open/Closed:Open => Closed ___ Follow-up Comment #9: If neither of us

[bug #24561] find -ok should not redirect stdin

Update of bug #24561 (project findutils): Status: Need Info => None ___ Follow-up Comment #6: Updating the state of the bug since I don't think it's blocking on a response from the origin

[bug #26701] if there are any funny characters, * no longer matches in certain locales

Update of bug #26701 (project findutils): Status: Need Info => None ___ Reply to this item at: ___

[bug #20561] find should complain more clearly on backtrack failure and abort

Follow-up Comment #2, bug #20561 (project findutils): If no response in a month, I'll close this bug. ___ Reply to this item at: ___ Message sent via/b

[bug #30972] False positive with -amin

Update of bug #30972 (project findutils): Status:None => Need Info ___ Reply to this item at: ___

[bug #28913] 4.4.2 xargs: Add command example to EXAMPLES section to demonstrate option -I

Update of bug #28913 (project findutils): Status: Need Info => Works For Me Open/Closed:Open => Closed ___ Follow-up Comment #4: For a complete i

[bug #30883] Test failures on Solaris

Update of bug #30883 (project findutils): Status:None => Need Info ___ Reply to this item at: ___

[bug #31005] -exec {} + and -execdir {} + are always true (but documentation does not say so)

Update of bug #31005 (project findutils): Status:None => Confirmed ___ Reply to this item at: ___

[bug #31265] anewer not working consistently

Update of bug #31265 (project findutils): Status:None => Need Info ___ Follow-up Comment #1: You aren't using findutils version 4.1.20, because that would say "4.1.20" in response to --v

[bug #30883] Test failures on Solaris

Follow-up Comment #1, bug #30883 (project findutils): I don't have access to any Solaris systems. Could you provide a system call trace identifying which system calls have failed and why? ___ Reply to this item at:

[bug #30972] False positive with -amin

Follow-up Comment #3, bug #30972 (project findutils): Please provide a short shell script which reproduces your problem (including setting up the initial conditions). Thanks. ___ Reply to this item at:

[bug #31005] -exec {} + and -execdir {} + are always true (but documentation does not say so)

Update of bug #31005 (project findutils): Assigned to:None => jay ___ Follow-up Comment #1: Yes, the documentation should mention this (and I'm surprised it doesn't already; sorry).