Dont most git instances, like github, delete branch after a PR was merged, by default? I am not sure under what usecases, you will end up with a lot of stale branches. And git fetch -pa should fix it locally
That seems to be largely grasped at straws and connecting dots without reason. For example oss-fuzz was building xz by cloning the github repo directly. There was never a chance for oss-fuzz to discover the backdoor,…
There are no code review on packets with 1 active maintainer.
This is very likely just a mistake and not deliberate. a) absolutely nobody uses cmake to build this packet b) if you try to build the packet with cmake and -DENABLE_SANDBOX=landlock, the build just fails:…
Dont most git instances, like github, delete branch after a PR was merged, by default? I am not sure under what usecases, you will end up with a lot of stale branches. And git fetch -pa should fix it locally
That seems to be largely grasped at straws and connecting dots without reason. For example oss-fuzz was building xz by cloning the github repo directly. There was never a chance for oss-fuzz to discover the backdoor,…
There are no code review on packets with 1 active maintainer.
This is very likely just a mistake and not deliberate. a) absolutely nobody uses cmake to build this packet b) if you try to build the packet with cmake and -DENABLE_SANDBOX=landlock, the build just fails:…