History log of /external/toybox/toys/posix/find.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
1f5f436826505df6dfabe1de9724424fc40fae23 10-May-2015 Rob Landley <rob@landley.net> Cleanups of dirtree_start() calls. (Don't need to feed in flag values, just
symfollow true/false.)
/external/toybox/toys/posix/find.c
aab9164df395a4b0878b0ad930a5ec8a806a58e9 10-May-2015 Rob Landley <rob@landley.net> Add DIRTREE_SHUTUP to disable dirtree warnings if file vanishes out from
under traversal. Pass through full flag set in dirtree_add_node(), add
dirtree_start() wrapper to provide symlink-only behavior (avoiding a lot
of DIRTREE_SYMFOLLOW*!!(logic) repeated in callers).
/external/toybox/toys/posix/find.c
33f04551f3c9a5182aabe9dfe36d6a0b88298686 21-Mar-2015 Rob Landley <rob@landley.net> Another bug from David Halls: find -exec wasn't consuming its argument when it didn't activate.

test: find . -name README -exec echo one '{}' ';' -or -exec echo two '{}' ';'
/external/toybox/toys/posix/find.c
be4048dd2509f2b9e968a4d03c06050d847971d3 12-Mar-2015 Rob Landley <rob@landley.net> Make find accept numeric uid/gid, and simplify makedevs using the new infrastructure.
/external/toybox/toys/posix/find.c
38e5485c6a8ece99aa8aac2f318f14764857ee24 03-Mar-2015 Rob Landley <rob@landley.net> On 64 bit, subtracting two pointers produces a long result. On 32 bit, it's an int. Even though long _is_ 32 bits on a 32 bit systems, gcc warns about it because reasons.

Also, the warning being that "expects int, but type is wchar_t"... no, type
is not wchar_t. Type is probably long. Specify the ACTUAL TYPE, not the random
typedef alias for it. If the translated type _did_ match, there wouldn't
be a warning! (This is why c89 promoted all arguments to int, precisely
so this wasn't a problem.)
/external/toybox/toys/posix/find.c
f6c28b6e0017ac36190ee31132721a1c9e30f2b6 22-Nov-2014 Rob Landley <rob@landley.net> As long as Android's going to require fortify, fixup the warnings it generates.
/external/toybox/toys/posix/find.c
a6336b942302b92f0b65ec35299e7667b9fcbe19 15-Sep-2014 Rob Landley <rob@landley.net> find -xdev should return mount points, just not contents.
/external/toybox/toys/posix/find.c
360d57f843f5435a75270e54583430dcb8f62546 14-Sep-2014 Rob Landley <rob@landley.net> Split xpopen() into xpopen_both(), xpopen(), and xrun() depending on whether we want to redirect both, one, or neither of stdin/stdout.
/external/toybox/toys/posix/find.c
6634e46216410161f0f56dc54b16da2de6a8f2b3 08-Sep-2014 Rob Landley <rob@landley.net> Add error test and fix memory leak, reported by Ashwini Sharma.
/external/toybox/toys/posix/find.c
c572530223ddad725e0f7606bf4b898d8f95f640 08-Aug-2014 Rob Landley <rob@landley.net> Fix -mindepth and -maxdepth to not drill down into excluded directories.

The fact other implementations don't implement "! -mindepth" doesn't mean we can't. Also, find uses +N, N, -N for everything else but this extension doesn't. Also, -depth already had a definition and this has nothing to do with that. It's a poorly thought-out extension, is what I'm saying.
/external/toybox/toys/posix/find.c
c39a337101de8613e71c5c474feb54297cce5eaa 06-Aug-2014 Rob Landley <rob@landley.net> More find bugfixes.
/external/toybox/toys/posix/find.c
5e4787ea3144364983944c38eb2a5ab2f12351bc 06-Aug-2014 Rob Landley <rob@landley.net> Rereading posix find.c page: "Specifying more than one of the mutually-exclusive options -H and -L shall not be considered an error. The last option specified shall determine the behavior of the utility."
/external/toybox/toys/posix/find.c
6804d2324ff2524cdf9ac013cb2b6b72c2295117 06-Aug-2014 Rob Landley <rob@landley.net> find.c: Posix wants loop detection.
/external/toybox/toys/posix/find.c
2c2eaba63fd42442453b1ad87fadc7d02532ea28 06-Aug-2014 Rob Landley <rob@landley.net> Building busybox from source needs find -not (a synonym for posix's "!").
/external/toybox/toys/posix/find.c
4edcd084f4782518249b888efc5d8f965bd5742e 05-Aug-2014 Rob Landley <rob@landley.net> find.c: add -mindepth, -maxdepth, and document -newer and -depth.
/external/toybox/toys/posix/find.c
60c35c486a2ea1c6ea8920c599abf992b27542c5 03-Aug-2014 Rob Landley <rob@landley.net> Implement exec -user, -group, and -newer. Enable find in defconfig.
/external/toybox/toys/posix/find.c
e686dcc30ba4505f813b9f5ccfa8ed9cf8644d3f 03-Aug-2014 Rob Landley <rob@landley.net> Unbreak find -exec.
/external/toybox/toys/posix/find.c
b3c2d1cd4ef97f200bb7b668ae4c3be06d59063c 31-Jul-2014 Rob Landley <rob@landley.net> find.c: fix -iname.
/external/toybox/toys/posix/find.c
fd14a61e941828c580bd476bb51f371f3d1ddf09 30-Jul-2014 Rob Landley <rob@landley.net> find.c: first pass at case case insensitivity and exec. (Needs more debugging.)
/external/toybox/toys/posix/find.c
a873444aa3e57d05c639c849a41a2add146f0309 19-Jul-2014 Rob Landley <rob@landley.net> Find bugfixes.

The check for -print vs -print0 was tested before I optimized out the "-" in the strcmps, and I didn't adjust the offset or retest it. (Ooops.)

Also, I wasn't clearing the ! value when descending into parentheticals, so "find . -name blah -o \! \( -stuff -o -thing \)" acted like it had a spurious second ! before -stuff inside the parentheses.
/external/toybox/toys/posix/find.c
fc7bc38af05fc882472d310a0b68648ed990ef2d 17-Jul-2014 Rob Landley <rob@landley.net> Write a new find. Not quite done, but the basics work.
/external/toybox/toys/posix/find.c