New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stubby: init at 0.2.1 #34975
stubby: init at 0.2.1 #34975
Conversation
Can't be built on macOS because of #34989. |
queries sent from a client machine (desktop or laptop) to a DNS | ||
Privacy resolver increasing end user privacy. Stubby is developed by | ||
the getdns team. | ||
''; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation, please, just as it was for getdns in the end https://github.com/NixOS/nixpkgs/pull/34921/files#diff-3f19f5b14f3dc0b7cdf83623bc28eb3cR25
Where is stubby and why is 6ec8fe0 pointing to my commit instead? |
I didnt merge this... |
w00t? |
@leenaars please tell me, you have closed this pull request at least. |
leenaars force-pushed the leenaars:stubby branch from 282b2b5 to 6ec8fe0 13 days ago
I think this might have triggered an automatic merging of the pull request, which is how people merge pull requests using the command line.
The logic to automatically merge a Pull Request looks at the commit SHA's present on the Pull Request.
If all of the commit SHA's have been pushed to the base branch already, we'll automatically mark it as merged.
Would it be the case that commits that are already present in the base branch NixOS:master were force pushed to the head branch leenaars:stubby, therefore producing what we see now?``` |
Motivation for this change
Stubby is a local stub resolver that implements RFC 7858, aka DNS-over-TLS. This allow private DNS requests.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)