Thomas Petazzoni ebe5d9edfe boot, package, support, toolchain: switch to 2 spaces for the hash file ... It's time to finally switch over globally to the new spacing format that we have agreed on for the hash file, with 2 spaces as a separator between fields. This commit was mechanically generated using: find . -type f -name '*.hash' | xargs sed -i 's%^md5[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%md5 \1 \2%' find . -type f -name '*.hash' | xargs sed -i 's%^sha1[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%sha1 \1 \2%' find . -type f -name '*.hash' | xargs sed -i 's%^sha256[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%sha256 \1 \2%' find . -type f -name '*.hash' | xargs sed -i 's%^sha512[ \t]*\([^ \t]*\)[ \t]*\(.*\)$%sha512 \1 \2%' This commit can easily be backported on the LTS branch by re-running the same commands, if needed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>		2022-07-28 23:05:23 +02:00
..
0001-Fix-build-without-Python.patch
0002-Fix-python-client-cross-compile.patch
0003-python-pkg-Fix-lirc-version-detection-when-cross-com.patch
0004-plugins-devinput.c-fix-build-with-musl-1.2.0.patch
Config.in
lirc-tools.hash
lirc-tools.mk
S25lircd