summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2019-11-15 08:50:43 -0800
committerGitHub <noreply@github.com>2019-11-15 08:50:43 -0800
commit8706c58ffa2dcf4598ce884ed9401662e6558fbb (patch)
tree5f1ef409f8317896ea1052f0e88c219031b4ca65 /RELEASE_NOTES.md
parentd92ec2c89bd8fcec3393d357a5656f7afa048562 (diff)
downloadchef-8706c58ffa2dcf4598ce884ed9401662e6558fbb.tar.gz
Update RELEASE_NOTES.md
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index afb313d26e..5f9be35ba6 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -10,7 +10,7 @@ For more information all all of the new helpers available, see the [chef-utils r
## Chefignore Improvements
-We've reworked how chefignore files are handled in knife, which has allowed us to close out a large number of long outstanding bugs. knife will now traverse all the way up the directory structure looking for a chefignore file. This means you can place a chefignore file in each cookkbook or any parent directory in your repository structure. Additionally we've made fixes that ensure that commmands like `knife diff` and `knife cookbook upload` always honor your chefignore files.
+We've reworked how chefignore files are handled in knife, which has allowed us to close out a large number of long outstanding bugs. knife will now traverse all the way up the directory structure looking for a chefignore file. This means you can place a chefignore file in each cookkbook or any parent directory in your repository structure. Additionally, we have made fixes that ensure that commmands like `knife diff` and `knife cookbook upload` always honor your chefignore files.
## Windows Habitat Plan