| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
Correct their descriptions to indicate that it is the contents of the
symbolic link that are matched.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
|
|
|
|
| |
the translation work.
|
|
|
|
| |
Noticed by: Vadim Goncharov <vadimnuclight tpu.ru>
|
|
|
|
|
|
| |
PR: docs/103859
Submitted by: shaun
MFC after: 1 week
|
| |
|
|
|
|
| |
-f pathname was specified.
|
|
|
|
|
|
|
|
|
| |
specified size to be read in the more familiar units of kilobytes,
megabytes, gigabytes, terabytes and petabytes.
PR: bin/50988
Submitted by: Matthew Seaman <m.seaman@infracaninophile.co.uk>
MFC after: 7 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
work with the st_birthtime field of struct stat.
'B' has been chosen to match the format specifier from stat(1).
Approved by: jhb
MFC after: 2 weeks
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
| |
in queryuser(). This allows users to respond to -ok and -okdir
prompts with any affirmative reply defined by their current locale.
|
| |
|
|
|
|
| |
entry from BUGS section that said otherwise.
|
|
|
|
| |
Pointed out by: simon
|
|
|
|
|
|
| |
options even though they look like primaries. (This is already documented
in the options themselves, but is sufficiently astonishing that I think it
deserves a BUGS entry as well.)
|
|
|
|
|
|
|
|
|
| |
section.
Move the HISTORY section to place it before BUGS rather than after BUGS,
in order to minimize the chance of this error being reproduced in the
future. (Both mdoc(7) and 63% of manual pages have these sections listed
in this order.)
|
| |
|
|
|
|
| |
by POSIX.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the depth of the current file relative to the starting
point of the traversal is n. The usual +/- modifiers
to the argument apply.
- while I'm here, fix -maxdepth in the case of a depth-first
traversal
Print the top ten maintainers of python module ports
(works with p5-* too):
find /usr/ports -depth 2 \! -name 'py-*' -prune -o \
-depth 3 -name Makefile -execdir make -VMAINTAINER \; \
| sort | uniq -c | sort -nr | head
PR: 66667
Reviewed by: ru, joerg
Approved by: joerg
MFC after: 2 weeks
|
|
|
|
|
| |
Fixed a bunch of hyphen misspellings.
Fixed one warning.
|
|
|
|
| |
Noticed by: ru
|
|
|
|
|
|
| |
PR: 66613
Approved by: ru
MFC after: 3 days
|
|
|
|
| |
PR: 65822
|
|
|
|
| |
Update date.
|
|
|
|
|
|
|
|
|
|
| |
1: Document -follow under COMPATIBILITY.
2: Update an example to be a little more 'safe'.
3: Use '/' in place of '.' for an example; similar to other manual pages.
PR: 40196 (1), 39532 (2, 3)
Submitted by: Marc Silver <marcs@draenor.org> (2 and 3)
Discussed with: des (1)
|
| |
|
|
|
|
|
|
|
|
| |
a shell.
PR: docs/54667
Submitted by: Patrick Alken <pa59@cornell.edu>
MFC after: 3 days
|
|
|
|
| |
Approved by: re
|
|
|
|
| |
Approved by: re
|
| |
|
|
|
|
|
| |
Obtained from: OpenDarwin
MFC after: 1 week
|
|
|
|
|
|
| |
in revision 1.17 of option.c.
MFC after: 1 week
|
|
|
|
| |
its own argument for -ok and -okdir.
|
|
|
|
|
| |
argument lists must be in an argument by itself, not on the end of the
previous one.
|
|
|
|
| |
SUSv3. This is similar to find foo -print0 | xargs -0 utility args.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
PR: 36602
Submitted by: Joshua Goodall <joshua@roughtrade.net>
No objections from: ru
MFC after: 2 days
|
|
|
|
|
|
| |
PR: docs/36601
Submitted by: Joshua Goodall <joshua@roughtrade.net>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
of time units to be used with -[acm]time primaries.
Based on patch from Nils M Holm <nmh@t3x.org>.
PR: bin/29165, bin/30309
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
documented behavior. Only a certain set of file flags were recognized,
and "no" flags did not match files that have corresponding flags bits
turned off.
Fix and extend the -flags functionality as follows:
: -flags [-|+]<flags>,<notflags>
: The flags are specified using symbolic names (see chflags(1)).
: Those with the "no" prefix (except "nodump") are said to be
: <notflags>. Flags in <flags> are checked to be set, and flags in
: <notflags> are checked to be not set. Note that this is different
: from -perm, which only allows the user to specify mode bits that
: are set.
:
: If flags are preceded by a dash (``-''), this primary evaluates
: to true if at least all of the bits in <flags> and none of the bits
: in <notflags> are set in the file's flags bits. If flags are pre-
: ceded by a plus (``+''), this primary evaluates to true if any of
: the bits in <flags> is set in the file's flags bits, or any of the
: bits in <notflags> is not set in the file's flags bits. Otherwise,
: this primary evaluates to true if the bits in <flags> exactly match
: the file's flags bits, and none of the <flags> bits match those of
: <notflags>.
MFC after: 2 weeks
|
|
|
|
| |
PR: docs/30237
|