Skip to content

Version 4.1.7

Latest

Choose a tag to compare

@tavianator tavianator released this 11 Nov 20:00
Immutable release. Only release title and notes can be modified.
4.1.7

Changes

  • Parallel depth-first searches (-S dfs -j3 and up) now stay much closer to depth-first order, rather than degrading towards breadth-first (c650271c)

Bug fixes

  • Fixed the traversal order of -S dfs when stat() calls weren't needed, which was not actually depth-first. The bug was originally introduced in bfs 3.1 (February 6, 2024). (fe6e2867)

  • Fixed -perm with X in symbolic modes like u+x,g+X, which now takes execute bits set earlier in the same mode into account. The bug had been present since -perm was implemented in bfs 0.84 (October 29, 2016). (c9be2981)

  • Fixed -perm with = in symbolic modes like u+s,u=r or o+t,o=r, which failed to clear the set-user-ID, set-group-ID, and sticky bits. As with GNU chmod, the set-user-ID and set-group-ID bits are still preserved for directories. The bug had been present since -perm was implemented in bfs 0.84 (October 29, 2016). (efdf3ad5)

  • Fixed and extended the mapping from C locale charsets to Oniguruma encodings for -regex (c3794ef0)

  • Fixed a missing error message when -files0-from failed to read from its file. The bug was originally introduced in bfs 2.6.3 (January 31, 2023). (17f5165c)

  • Fixed a redundant error message when closing a file after a write error had already been reported, as in

    $ bfs -print -exec true \; >/dev/full
    

    The bug was originally introduced in bfs 3.3 (May 28, 2024). (2c970dbd)