archwiki: use a drop-in file for memcached@.service instead of an entirely custom unit
All threads resolved!
This allows to retain all default hardening options that memcached@.service
has.
Edited by nl6720
Merge request reports
Activity
added 11 commits
-
52443215...9429815c - 10 commits from branch
archlinux:master
- f6a3ced0 - archwiki: use a drop-in file for memcached.service instead of an entirely custom unit
-
52443215...9429815c - 10 commits from branch
added 19 commits
-
f6a3ced0...f151b734 - 18 commits from branch
archlinux:master
- 693c634f - archwiki: use a drop-in file for memcached.service instead of an entirely custom unit
-
f6a3ced0...f151b734 - 18 commits from branch
- Resolved by nl6720
added 1 commit
- 615e665d - archwiki: use a drop-in file for memcached.service instead of an entirely custom unit
added 40 commits
-
615e665d...d6722ad8 - 38 commits from branch
archlinux:master
- 6d879cca - archwiki: use a drop-in file for memcached.service instead of an entirely custom unit
- 6d9edcb8 - fixup! archwiki: use a drop-in file for memcached.service instead of an entirely custom unit
-
615e665d...d6722ad8 - 38 commits from branch
- Resolved by nl6720
Deployed with a suggestion from @foutrelis to use
memcached@
. @nl6720 can you squash? and then we can merge.
- Resolved by nl6720
added 1 commit
- 8ed4b9bf - archwiki: use a drop-in file for memcached.service instead of an entirely custom unit
added 1 commit
- cb89551f - archwiki: use a drop-in file for memcached@.service instead of an entirely custom unit
mentioned in commit cfd55fcf
Please register or sign in to reply