diff options
| author | Tavian Barnes <tavianator@tavianator.com> | 2022-03-26 15:36:37 -0400 |
|---|---|---|
| committer | Tavian Barnes <tavianator@tavianator.com> | 2022-03-26 15:39:00 -0400 |
| commit | d0565f9830b483d8f307e966e22fde01478b26df (patch) | |
| tree | cb545a02b780d917880fa5474277b2bf1ac0c0a5 /printf.c | |
| parent | 30e55d140074749809c419bba2a1a9fd1a4c7de9 (diff) | |
| download | bfs-d0565f9830b483d8f307e966e22fde01478b26df.tar.xz | |
parse: Stop warning for options after tests/actions
Part of the bfs design philosophy is to care less about the order of
arguments. As such, there's no good reason to be warning-compatible
with GNU find in this case. I don't even think things like this are
confusing:
bfs -print -color
so why warn about it?
Diffstat (limited to 'printf.c')
0 files changed, 0 insertions, 0 deletions