diff options
| author | Oleksandr Kuchmystyi <o.kuchmystyi@vyos.io> | 2025-07-22 13:05:38 +0300 |
|---|---|---|
| committer | Oleksandr Kuchmystyi <o.kuchmystyi@vyos.io> | 2025-07-22 13:05:38 +0300 |
| commit | 71ade9dce3bfbf9dd8e608eb43ad47896c2045a5 (patch) | |
| tree | 10a551bc2665f67f8dd252fc3931886c83f96099 /scripts/package-build/linux-kernel | |
| parent | 28147b458689b338a25b5bb17d650956c6f37745 (diff) | |
| download | vyos-build-71ade9dce3bfbf9dd8e608eb43ad47896c2045a5.tar.gz vyos-build-71ade9dce3bfbf9dd8e608eb43ad47896c2045a5.zip | |
T7576: Remove unnecessary code for checking dirty build status
```
vyos@r15:~$ show version | match dir
Build commit ID: d8038ded37fadb-dirty
```
Having uncommited files in vyos-build is completely normal:
custom configs, EULA files in official release builds,
anything else that flavor files may include.
However, many people are not familiar with the specific
meaning of "dirty" in git or with the build process and assume
that "dirty" means something went wrong with the image build.
Diffstat (limited to 'scripts/package-build/linux-kernel')
0 files changed, 0 insertions, 0 deletions