diff options
author | Tavian Barnes <tavianator@tavianator.com> | 2020-06-08 12:37:44 -0400 |
---|---|---|
committer | Tavian Barnes <tavianator@tavianator.com> | 2020-06-08 14:07:02 -0400 |
commit | 9e087babb7b95af5684d46f47cb99f223432dfe1 (patch) | |
tree | 2f8cb2fa035e966bc1dd03711f3a12c8ae9a9131 /RELEASES.md | |
parent | bdc51f99c9033b758223404003cdcb11e85f23bd (diff) | |
download | bfs-9e087babb7b95af5684d46f47cb99f223432dfe1.tar.xz |
RELEASES.md: Add some 2.0 release notes
Diffstat (limited to 'RELEASES.md')
-rw-r--r-- | RELEASES.md | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/RELEASES.md b/RELEASES.md index 11f5bc8..898bacd 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -1,3 +1,39 @@ +2.* +=== + +2.0 +--- + +**Unreleased** + +- New `-exclude <expression>` syntax to more easily and reliably filter out paths (#8). + For example: + + bfs -name config -exclude -name .git + + will find all files named `config`, without searching any directories (or files) named `.git`. + In this case, the same effect could have been achieved (more awkwardly) with `-prune`: + + bfs ! \( -name .git -prune \) -name config + + But `-exclude` will work in more cases: + + # -exclude works with -depth, while -prune doesn't: + bfs -depth -name config -exclude -name .git + + # -exclude applies even to paths below the minimum depth: + bfs -mindepth 3 -name config -exclude -name .git + +- `-nohidden` is now equivalent to `-exclude -hidden`. + This changes the behavior of command lines like + + bfs -type f -nohidden + + to do what was intended (#30). + +- Fixed an optimizer bug that could skip `-empty`/`-xtype` if they didn't always lead to an action + + 1.* === |