diff options
author | Adrian Freihofer <adrian.freihofer@gmail.com> | 2024-02-15 23:53:32 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-02-19 11:34:33 +0000 |
commit | a510d455d3b93e2d7c5e1aef7b2dbe7d77d6a03d (patch) | |
tree | 42b04aadbfd407dbe4890377f199ae405f18a357 /meta/classes-recipe | |
parent | 09839f6a8a7be68d133170ce9b2decf2fa99144b (diff) | |
download | poky-a510d455d3b93e2d7c5e1aef7b2dbe7d77d6a03d.tar.gz |
vscode: drop .vscode folder
There is a new official bitbake plugin:
https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake
This plugin automatically updates the .vscode/settings.json file.
Having the settings.json file in git and a plugin which modifies this
file is not ideal. It can lead to anoying situations especially when
working with git. For example a git stash reverts the settings which are
automatically applied by the plugin. While git stashed the settings.json
file the plugin immediately changes the file again and tries to run
bitbake based on the newly generated settings. When git does a stash pop
the restored settings.json file conflicts with the new settigns.json
file which has been generated while the git stash took place.
Therefore this patch removes the .vscode folder from git.
Removing the settings.json leads to other issues as already described
in the commit message of 5ff688fe29. But we still need another solution
where the settings.json file is not in Git.
Discussion is here:
https://github.com/yoctoproject/vscode-bitbake/issues/95
(From OE-Core rev: f36771e155b9e0cf24a885bf3340d59036aa42c5)
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes-recipe')
0 files changed, 0 insertions, 0 deletions