| Commit message (Collapse) | Author | Age |
... | |
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |/ /
| | |
| | |
| | | |
blacklisted
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
[skip ci]
|
| | |
| | |
| | |
| | | |
See https://github.com/netblue30/firejail/commit/00cb8b611f0e35a56585061d689fbcca2af0566b#commitcomment-53262808
|
| |\ \
| | | |
| | | | |
Create profcleaner.sh
|
| | | |
| | | |
| | | | |
[skip ci]
|
| | | |
| | | |
| | | |
| | | | |
profcleaner.c is just sed, I was wondering why we need C for that.
|
| |\ \ \
| | | | |
| | | | | |
allow/deny in zsh completion
|
| | |/ / |
|
| |\ \ \
| | | | |
| | | | | |
Exclude allow/deny move in profile from git blame
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
fe0f975f447d59977d90c3226cc8c623b31b20b3 (move whitelist/blacklist to
allow/deny) is just a huge rename w/o effects to the profile. Ignoreing
it in git blame to see which commits actually added/changed a
allow/nodeny command.
Configure git to use .git-blame-ignore-revs:
git config blame.ignoreRevsFile .git-blame-ignore-revs
|
| |\ \ \
| | | | |
| | | | | |
Update Clion profile and Add Clion EAP profile
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ /
| | | |
| | | |
| | | |
| | | | |
Add new clion-eap profile
Fix broken clion profile
|
| |\ \ \
| | |/ /
| |/| | |
LC_ALL=C sort disable-programs.inc
|
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
whitelist/nowhitelist/blacklist/noblacklist
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | | |
Fix sndio support
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | | |
Co-authored-by: rusty-snake <41237666+rusty-snake@users.noreply.github.com>
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
Refactor bitwarden as electron redirect
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
gcov: use no-op functions if not enabled
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Instead of wrapping every gcov function call in an ifdef.
Note: The usage of `((void)0)` is based on section 7.2 of the C99
standard (N1256)[1] [2]:
> 7.2 Diagnostics <assert.h>
>
> 1 The header <assert.h> defines the assert macro and refers to another
> macro,
>
> NDEBUG
>
> which is not defined by <assert.h>. If NDEBUG is defined as a macro
> name at the point in the source file where <assert.h> is included, the
> assert macro is defined simply as
>
> #define assert(ignore) ((void)0)
See also assert.h(0p) from POSIX.1-2017[3].
Note: This is a continuation of commit b408b20c7 ("gcov: fix build
failure with gcc 11.1.0") / PR #4373.
[1] http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1256.pdf
[2] https://port70.net/~nsz/c/c99/n1256.html#7.2
[3] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/assert.h.html
|