-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: miekg/dns
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.1.48
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: miekg/dns
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.1.49
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 6 files changed
- 3 contributors
Commits on Apr 2, 2022
-
Fix ExamplePrivateHandle (#1354)
Signed-off-by: Miek Gieben <miek@miek.nl>
Configuration menu - View commit details
-
Copy full SHA for dedee46 - Browse repository at this point
Copy the full SHA dedee46View commit details
Commits on Apr 12, 2022
-
* Add SVCB dohpath key The parameter is being added in [its own IETF draft][1] and also being used in the [IETF draft about Descovery of Designated Resolvers][2]. Additionally, the mappings of the numeric key values to strings are exported, under names consistent with the already existing exported mappings, to make it easier for the clients of the module to validate and print SVCB keys. Testing was done by sending SVCB queries for the "_dns.resolver.arpa" domain to OpenDNS's 146.112.41.2 server. [1]: https://datatracker.ietf.org/doc/html/draft-ietf-add-svcb-dns-02 [2]: https://datatracker.ietf.org/doc/html/draft-ietf-add-ddr-06.html * Fix template length, docs; reverse some changes * Remove incorrect validations; improve docs
Configuration menu - View commit details
-
Copy full SHA for 08c2616 - Browse repository at this point
Copy the full SHA 08c2616View commit details
Commits on Apr 14, 2022
-
Add notes about SVCB draft changes to SVCB-related API (#1364)
* Add notes about SVCB draft changes to SVCB-related API * Decrease number of warnings, rephrase
Configuration menu - View commit details
-
Copy full SHA for 656b740 - Browse repository at this point
Copy the full SHA 656b740View commit details
Commits on Apr 15, 2022
-
Configuration menu - View commit details
-
Copy full SHA for c760d3c - Browse repository at this point
Copy the full SHA c760d3cView commit details -
Upgrade our test Go version to 1.17 and 1.18 (#1369)
Signed-off-by: Miek Gieben <miek@miek.nl>
Configuration menu - View commit details
-
Copy full SHA for 0d2c95b - Browse repository at this point
Copy the full SHA 0d2c95bView commit details
Commits on May 10, 2022
-
Properly parse alpn values in SVCB (#1363)
* Modify the SVCBAlpn to properly parse/print * Remove debug * Change SVCB test from reflect to loop * Refactor SVCB code to reduce indentation * When stringifying SVCBAlpn, use strings.Builder for whole process * Update comment in svcb.go Co-authored-by: Miek Gieben <miek@miek.nl> * Describe why we use a specific size for the alpn buffer Co-authored-by: Miek Gieben <miek@miek.nl>
Configuration menu - View commit details
-
Copy full SHA for feda877 - Browse repository at this point
Copy the full SHA feda877View commit details -
Fix dohpath parsing/stringify (#1366)
* dohpath escaped in String(), and parsed such values * Update the test for dohpath with escaping * Fix cut & paste error with svcdohpath error
Configuration menu - View commit details
-
Copy full SHA for bfcbf0f - Browse repository at this point
Copy the full SHA bfcbf0fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5521648 - Browse repository at this point
Copy the full SHA 5521648View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.1.48...v1.1.49