diff options
| author | Rasmus Villemoes <ravi@prevas.dk> | 2025-01-29 09:37:50 +0100 |
|---|---|---|
| committer | Rasmus Villemoes <ravi@prevas.dk> | 2025-01-29 09:40:23 +0100 |
| commit | 0602af4c78ef5a6ee5e64d2cf9202c22aa636b25 (patch) | |
| tree | d5194077f414b6b793f012c2b0fff22a8c4357fd /dynamic-layers/qt5-layer/git@git.enea.com:linux | |
| parent | 4738bf97f8d95fe8d25fbdf1bde8c268c376e23f (diff) | |
| download | meta-freescale-0602af4c78ef5a6ee5e64d2cf9202c22aa636b25.tar.gz | |
scripts: avoid pointless LICENSE churn
I was wondering why a bot decided to force-push a commit to a PR of
mine. It turns out the script responsible for generating the LICENSE
file is not deterministic, so depending on random file system layout
we can end up regenerating the LICENSE without any actual change. For
example:
$ diff -u <(git show baf20676~1:LICENSE | sort) <(git show baf20676:LICENSE | sort)
shows that baf20676 didn't provide any change at all in the actual
contents, yet
$ git show --stat baf20676
commit baf20676bcd2b454577449dbf7b0346d7080b880
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Date: Wed Jan 22 21:42:44 2025 +0000
Auto-update LICENSE file with current recipe licenses
LICENSE | 256 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------
1 file changed, 128 insertions(+), 128 deletions(-)
Diffstat (limited to 'dynamic-layers/qt5-layer/git@git.enea.com:linux')
0 files changed, 0 insertions, 0 deletions