fix: remove unicode from used files

No considering license, copyright notices kept outside of the installed
directories, but excluding keys that have unicode in their comment
section.
This commit is contained in:
Ben Grande 2024-01-18 15:23:52 +01:00
parent f8ea066b2b
commit 0887c24a19
3 changed files with 7 additions and 7 deletions

View File

@ -20,7 +20,7 @@ set -eu
usage(){
echo "Usage: ${0##*/} --i-like-danger <DEVICE>"
echo "Example: ${0##*/} --i-like-danger 0000:00:1b.0"
echo "Warning: It is strongly discouraged to reattach PCI devices to dom0, especially if they dont support resetting!"
echo "Warning: It is strongly discouraged to reattach PCI devices to dom0, especially if they don't support resetting!"
exit 1
}

View File

@ -80,7 +80,7 @@ If you need to pull new commits, set `GNUPGHOME` to
verification on git merges:
```sh
GNUPGHOME="$HOME/.gnupg/qubes-builder" git pull
Commit 7c37bb7 has a good GPG signature by Frédéric Pierret (fepitre)
Commit 7c37bb7 has a good GPG signature by Frederic Pierret (fepitre)
<frederic.pierret@qubes-os.org>
...
```

View File

@ -246,16 +246,16 @@ FollowIndexFileRemoval: 1
#
# The following patterns are available for the purposes detailed, where
# the latter takes precedence over the former:
# - «PFilePattern» for static data that doesn't change silently on the server.
# - «VFilePattern» for volatile data that may change like every hour. Files
# - <PFilePattern> for static data that doesn't change silently on the server.
# - <VFilePattern> for volatile data that may change like every hour. Files
# that match both PFilePattern and VfilePattern will be treated as volatile.
# - Static data with file names that match VFilePattern may be overriden being
# treated as volatile by making it match the special static data pattern,
# «SPfilePattern».
# - «SVfilePattern» or the "special volatile data" pattern is for the
# <SPfilePattern>.
# - <SVfilePattern> or the "special volatile data" pattern is for the
# convenience of specifying any exceptions to matches with SPfilePattern,
# for cases where data must still be treated as volatile.
# - «WfilePattern» specifies a "whitelist pattern" for the regular expiration
# - <WfilePattern> specifies a "whitelist pattern" for the regular expiration
# job, telling it to keep the files even if they are not referenced by
# others, like crypto signatures with which clients begin their downloads.
#