feat: kubesphere 4.0 (#6115)
* feat: kubesphere 4.0 Signed-off-by: ci-bot <ci-bot@kubesphere.io> * feat: kubesphere 4.0 Signed-off-by: ci-bot <ci-bot@kubesphere.io> --------- Signed-off-by: ci-bot <ci-bot@kubesphere.io> Co-authored-by: ks-ci-bot <ks-ci-bot@example.com> Co-authored-by: joyceliu <joyceliu@yunify.com>
This commit is contained in:
committed by
GitHub
parent
b5015ec7b9
commit
447a51f08b
19
vendor/github.com/kevinburke/ssh_config/CHANGELOG.md
generated
vendored
Normal file
19
vendor/github.com/kevinburke/ssh_config/CHANGELOG.md
generated
vendored
Normal file
@@ -0,0 +1,19 @@
|
||||
# Changes
|
||||
|
||||
## Version 1.2
|
||||
|
||||
Previously, if a Host declaration or a value had trailing whitespace, that
|
||||
whitespace would have been included as part of the value. This led to unexpected
|
||||
consequences. For example:
|
||||
|
||||
```
|
||||
Host example # A comment
|
||||
HostName example.com # Another comment
|
||||
```
|
||||
|
||||
Prior to version 1.2, the value for Host would have been "example " and the
|
||||
value for HostName would have been "example.com ". Both of these are
|
||||
unintuitive.
|
||||
|
||||
Instead, we strip the trailing whitespace in the configuration, which leads to
|
||||
more intuitive behavior.
|
||||
Reference in New Issue
Block a user