Age | Commit message (Expand) | Author |
2013-04-23 | handle large ino_t; ok millert | Theo de Raadt |
2013-04-20 | adjust comment | Theo de Raadt |
2013-04-19 | handle large numbers. this fixes time_t beyond 2038, constrains the | Theo de Raadt |
2013-03-14 | -follow is the same as -L, not -H | Alexander Hall |
2012-12-05 | Remove excessive sys/cdefs.h inclusion | Theo de Raadt |
2012-01-05 | -execdir only supports the first form of -exec with ; suffix, not the new | Stuart Henderson |
2012-01-05 | Fix typos in comment (s,exacty,exactly,) | Stuart Henderson |
2012-01-03 | - use more consistent markup | Jason McIntyre |
2012-01-02 | Add support for "find ... -exec foo {} \+". | Pascal Stumpf |
2011-06-14 | exit if there is an unknown option; from FreeBSD | Christian Weisgerber |
2011-04-21 | find: return exit code 1 if any path could not be traversed | Jacek Masiulaniec |
2011-02-13 | As noticed by Clint Pachl <pachl at ecentryx dot com>, | Ingo Schwarze |
2010-12-01 | Don't error out if we can't opendir() when -empty is used. | Todd C. Miller |
2010-09-29 | various EXIT STATUS fixes; from Daniel Dickman | Jason McIntyre |
2010-09-20 | oops! missing quote in previous; | Jason McIntyre |
2010-09-19 | Shorten text pointing from -X to -print0. | Ingo Schwarze |
2010-07-15 | More delimiters that need quoting inside macros, hunted down by jmc@, | Ingo Schwarze |
2010-02-03 | make it clear that -iname supports globbing; | Ingo Schwarze |
2009-12-20 | Use the standard wording, requested by jmc@. | Ingo Schwarze |
2009-12-20 | find -LH was -L, but must be -H according to POSIX; | Ingo Schwarze |
2009-12-09 | We only need to fchdir(dotfd) for the -exec and -ok primaries so | Todd C. Miller |
2009-10-28 | rcsid[] and sccsid[] and copyright[] are essentially unmaintained (and | Theo de Raadt |
2009-09-16 | Allow -maxdepth 0; noticed by bluhm@ | Todd C. Miller |
2009-08-27 | Don't stop traversing a directory hierarchy if we reach SHRT_MAX, | Todd C. Miller |
2009-04-09 | min/maxdepth do not observe +-; | Jason McIntyre |
2009-02-08 | updates to IEEE Std 1003.1-2008; | Jason McIntyre |
2009-02-08 | bump the posix reference in STANDARDS to IEEE Std 1003.1-2008, with a few | Jason McIntyre |
2009-01-28 | since -g is always overridden by -l in ls(1), the equivalent of the | Jason McIntyre |
2008-09-29 | Add a missing `|' to the description of -perm. | Matthias Kilian |
2007-05-31 | convert to new .Dd format; | Jason McIntyre |
2007-05-30 | - use a consistent text for STANDARDS | Jason McIntyre |
2007-05-10 | ftsopen -> fts_open; partly from Alexander Holupirek, documentation/5472 | Jason McIntyre |
2006-12-26 | fts_read returning NULL and errno set is an error. ok ray@ | Otto Moerbeek |
2006-10-11 | hmm, slightly reword the previous to sound less like a susv3 cut/paste, | Jason McIntyre |
2006-10-11 | some important information about how find(1) works was tucked away | Jason McIntyre |
2006-10-11 | improve markup a wee bit; | Jason McIntyre |
2006-10-11 | a little macro cleanup; | Jason McIntyre |
2006-10-11 | Suggest to use xargs(1) and give an example; started by jmc, ok jmc@ | Otto Moerbeek |
2006-10-11 | in EXAMPLES: | Jason McIntyre |
2006-10-11 | for -depth, -follow, and -xdev, note that they always evaluate to true; | Jason McIntyre |
2006-10-10 | get the spacing right for -ok too; i missed this in my previous commit. | Jason McIntyre |
2006-10-10 | get the spacing right for -exec and -execdir; ok otto | Jason McIntyre |
2006-10-10 | add an example of -exec {} and remove a less useful example; ok otto | Jason McIntyre |
2006-10-05 | -iname is a primary, not an option. ok jmc@ | Otto Moerbeek |
2006-10-05 | document -depth and -xdev: although we have options which do the same, | Jason McIntyre |
2006-10-04 | - bump latest posix version | Jason McIntyre |
2006-10-02 | remove some unneccessary escaping; | Jason McIntyre |
2006-10-01 | rewrite the piece about separate arguments to not confuse jmc@. | Otto Moerbeek |
2006-09-26 | clear up some confusion between operands and operators; with & ok jmc@ | Otto Moerbeek |
2006-09-24 | do not suggest that !expression and (expression) (without spaces) is valid; | Jason McIntyre |