summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Keep track of required FDs per-exprTavian Barnes2017-12-155-16/+35
|
* exec: Minor whitespace consistency fixTavian Barnes2017-11-131-1/+1
|
* color: Optimize cfprintf() a bitTavian Barnes2017-11-131-76/+86
|
* color: Implement %m for cfprintf()Tavian Barnes2017-11-135-11/+19
|
* exec: Fix error reportingTavian Barnes2017-11-121-5/+9
|
* exec: Recover from E2BIGTavian Barnes2017-11-126-20/+135
|
* cmdline: Account for files opened during/between evaluations more carefullyTavian Barnes2017-11-123-9/+26
|
* Add support for file birth/creation times on platforms that have itTavian Barnes2017-11-057-60/+145
| | | | Fixes #19
* parse: Support -perm +7777, for compatibility with BSD and old GNU findTavian Barnes2017-11-054-5/+28
|
* Release 1.1.41.1.4Tavian Barnes2017-10-273-2/+13
|
* exec: Make argument size tracking robust to page-granularity accountingTavian Barnes2017-10-261-3/+8
| | | | | | | | From looking at the Linux exec() implementation, it seems a big part of the reason we needed extra headroom was that the arguments/environment are copied page-by-page, so even a small accounting difference could result in an error of an entire page size. Grow the headroom to two entire pages to account for this.
* exec: Apply more headroom to avoid E2BIGTavian Barnes2017-10-221-4/+16
| | | | | | | | | | | | | I ran into "argument list too long" errors with a bfs -type f -exec grep pattern '{}' + command, despite the current accounting being pretty careful. Some experimentation showed that an additional 2048 bytes of headroom is always safe. While we're at it, explicitly account for the terminating NULL pointers in argv and environ.
* Use "error:" prefix consistentlyTavian Barnes2017-10-221-4/+4
|
* cmdline: Declare functions in a more natural orderTavian Barnes2017-10-211-7/+7
|
* parse: Keep track of what files are already openTavian Barnes2017-10-216-50/+185
| | | | Fixes #22
* Report errors that occur when closing filesTavian Barnes2017-10-216-11/+60
| | | | Otherwise we miss write errors that occur when flushing the cache.
* Add a man pageTavian Barnes2017-10-153-15/+686
| | | | Fixes #31
* Don't use install -DTavian Barnes2017-10-131-3/+6
| | | | | | -D isn't portable to non-GNU Unices, so just use mkdir manually. Fixes #28
* Release 1.1.31.1.3Tavian Barnes2017-10-043-2/+11
|
* tests: -quit is not POSIXTavian Barnes2017-09-201-1/+1
|
* util: Wrap faccessat() to fix some portability issuesTavian Barnes2017-09-204-2/+21
|
* opt: More -O4 tweaksTavian Barnes2017-09-171-24/+15
|
* opt: Use the standard LLONG_MAX instead of the nonstandard LONG_LONG_MAXTavian Barnes2017-09-171-1/+1
|
* opt: Fix -depth with arguments bigger than INT_MAXTavian Barnes2017-09-173-4/+32
|
* opt: Move some aggressive optimizations back to -O4Tavian Barnes2017-09-172-18/+19
|
* parse: Document the bfs meaning of -O in -helpTavian Barnes2017-09-171-2/+15
|
* opt: Have data flow analysis respect always_{true,false}Tavian Barnes2017-09-171-6/+21
|
* tests: Add tests that trigger some optimizationsTavian Barnes2017-09-169-0/+87
|
* opt: Implement some data flow optimizationsTavian Barnes2017-09-161-108/+322
|
* opt: Separate optimization from parsingTavian Barnes2017-09-1611-665/+859
|
* Release 1.1.21.1.2Tavian Barnes2017-09-103-2/+14
|
* eval: Make sure nopenfd >= 2 for bftw()Tavian Barnes2017-09-091-6/+5
|
* tests: Silence error messages while creating deep/Tavian Barnes2017-09-091-1/+1
| | | | | Some platforms will print errors like "cannot access parent directories: Result too large"
* Try /proc/self/fd before /dev/fdTavian Barnes2017-09-092-5/+14
| | | | On Solaris, /proc/self/fd is dynamic while /dev/fd is static.
* mtab: Add support for SolarisTavian Barnes2017-09-091-0/+43
|
* Revert "tests: Test hardlinks to symlinks"Tavian Barnes2017-09-0713-20/+0
| | | | | | Apparently macOS doesn't support ln -P. This reverts commit 80eec18020f531abbdb2abbb919ab6c6fa34107c.
* parse: Don't reorder or remove tests with potential side effectsTavian Barnes2017-09-063-3/+29
| | | | | | -empty and -xtype may have side effects like reporting permission errors, which even affect the exit status of bfs. We shouldn't remove these effects without -Ofast.
* util: Factor out checks for nonexistent paths/broken linksTavian Barnes2017-09-063-3/+12
|
* parse: Factor out common initialization code for -print and friendsTavian Barnes2017-09-061-35/+30
|
* tests: Test hardlinks to symlinksTavian Barnes2017-09-0613-0/+20
|
* tests: Make test_deep pass with other find implementationsTavian Barnes2017-09-043-22/+37
| | | | | And move test_deep_strict to the bfs-specific tests, since it's not likely to ever pass for other implementations.
* Implement -D searchTavian Barnes2017-09-023-6/+111
|
* tests: Use human-readable filenames in links/Tavian Barnes2017-09-0233-142/+128
|
* mtab: Use __has_include() to check for <mntent.h>Tavian Barnes2017-09-021-4/+15
| | | | | This fixes the build against musl, as long as you have a new enough compiler for __has_include.
* Implement cost-based optimizationTavian Barnes2017-08-275-61/+254
|
* printf: Save some lines in time specifier parsingTavian Barnes2017-08-271-36/+4
|
* Avoid multiple extra stat()s of broken symlinks for -xtypeTavian Barnes2017-08-225-13/+18
|
* tests: Remove unnecessary sort-args.sh invocationsTavian Barnes2017-08-163-40/+40
|
* tests: Add some syntax highlighting to --verboseTavian Barnes2017-08-121-3/+22
|
* Unify broken symlink handlingTavian Barnes2017-08-1211-33/+74
| | | | | | | | | Rather than open-code the fallback logic for broken symlinks everywhere it's needed, introduce a new xfstatat() utility function that performs the fallback automatically. Using xfstatat() consistently fixes a few bugs, including cases where broken symlinks are given as arguments to predicates like -samefile.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-05 09:32:36 +0000