Follow-up Comment #2, bug #50058 (project findutils):
Hmmm, point taken. (The application I'm debugging has a couple base dirs and
puts the actual files a fixed number of directories, named per hash values,
underneath them, so the question didn't come up for me.)
However, the problem isn't *entirely* new. For cases where the processing
order of directories may influence the result, find already provides the
-depth option. Also, the order of files within a single directory remains
officially undefined, though it may show in the output.
Unless I'm missing something, the case you present would yield an unambiguous
result as soon as it were pinpointed whether, within a single directory, find
shall process "files before subdirs" (-> result: A2) or "subdirs before files"
(-> result: A1a and A2).
... that raises the question, however, whether find's code does or could obey
such a search order, as of now?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50058>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
