|
72.
|
|
|
actions: -delete -print0 -printf FORMAT -fprintf FILE FORMAT -print
-fprint0 FILE -fprint FILE -ls -fls FILE -prune -quit
-exec COMMAND ; -exec COMMAND {} + -ok COMMAND ;
-execdir COMMAND ; -execdir COMMAND {} + -okdir COMMAND ;
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
actions: -delete -print0 -printf FORMAT -fprintf FILE FORMAT -print
-fprint0 FILE -fprint FILE -ls -fls FILE -prune -quit
-exec COMMAND ; -exec COMMAND {} + -ok COMMAND ;
-execdir COMMAND ; -execdir COMMAND {} + -okdir COMMAND ;
|
|
Translated and reviewed by
Benjamin Goodger
|
|
|
|
Located in
find/parser.c:1131
|
|
73.
|
|
|
Report (and track progress on fixing) bugs via the findutils bug-reporting
page at http://savannah.gnu.org/ or, if you have no web access, by sending
email to <bug-findutils@gnu.org>.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
Report (and track progress on fixing) bugs via the findutils bug-reporting
page at http://savannah.gnu.org/ or, if you have no web access, by sending
email to <bug-findutils@gnu.org>.
|
|
Translated and reviewed by
Benjamin Goodger
|
|
|
|
Located in
find/parser.c:1261
|
|
74.
|
|
|
sanity check of the fnmatch() library function failed.
|
|
|
|
sanity check of the fnmatch() library function failed.
|
|
Translated and reviewed by
Benjamin Goodger
|
|
|
|
Located in
find/parser.c:1261
|
|
75.
|
|
|
warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '%s %s ' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ %s '.
|
|
|
|
warning: UNIX filenames usually don't contain slashes (though pathnames do). That means that '%s %s ' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ %s '.
|
|
Translated and reviewed by
Benjamin Goodger
|
|
|
|
Located in
find/parser.c:1264
|
|
76.
|
|
|
Expected a positive decimal integer argument to %s , but got %s
|
|
|
|
Expected a positive decimal integer argument to %s , but got %s
|
|
Translated and reviewed by
Adam Collard
|
|
|
|
Located in
find/parser.c:1399
|
|
77.
|
|
|
This system does not provide a way to find the birth time of a file.
|
|
|
|
This system does not provide a way to find the birth time of a file.
|
|
Translated by
Adam Collard
|
|
Reviewed by
Robert Readman
|
|
|
|
Located in
find/parser.c:1564
|
|
78.
|
|
|
The %s test needs an argument
|
|
|
|
The %s test needs an argument
|
|
Translated and reviewed by
Robert Readman
|
|
|
|
Located in
find/parser.c:1585
|
|
79.
|
|
|
I cannot figure out how to interpret %s as a date or time
|
|
|
|
I cannot figure out how to interpret %s as a date or time
|
|
Translated and reviewed by
Adam Collard
|
|
|
|
Located in
find/parser.c:1622
|
|
80.
|
|
|
Cannot obtain birth time of file %s
|
|
|
|
Cannot obtain birth time of file %s
|
|
Translated by
Adam Collard
|
|
Reviewed by
Robert Readman
|
|
|
|
Located in
find/parser.c:1639
|
|
81.
|
|
|
Mode %s is not valid when POSIXLY_CORRECT is on.
|
|
|
|
Mode %s is not valid when POSIXLY_CORRECT is on.
|
|
Translated and reviewed by
Adam Collard
|
|
|
|
Located in
find/parser.c:1779
|