-
Notifications
You must be signed in to change notification settings - Fork 87
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
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: http-rs/http-types
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: http-rs/http-types
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: typed-headers
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 64 files changed
- 1 contributor
Commits on Feb 7, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 324e947 - Browse repository at this point
Copy the full SHA 324e947View commit details -
Configuration menu - View commit details
-
Copy full SHA for c99a9e0 - Browse repository at this point
Copy the full SHA c99a9e0View commit details
Commits on Jun 18, 2022
-
Replace the use of "header" terminology with "field"
From https://www.rfc-editor.org/rfc/rfc9110.html#section-6.3: > 6.3. Header Fields > Fields (Section 5) that are sent or received before the content are referred to as "header fields" (or just "headers", colloquially). > The "header section" of a message consists of a sequence of header field lines. Each header field might modify or extend message semantics, describe the sender, define the content, or provide additional context. > Note: We refer to named fields specifically as a "header field" when they are only allowed to be sent in the header section. This means that our use of "header" is currently wrong. Because "fields" can be sent in both the headers and trailers section, solely referring to them as "headers" is wrong. We can work around confusion by linking to "headers" using a doc alias.
Configuration menu - View commit details
-
Copy full SHA for d912010 - Browse repository at this point
Copy the full SHA d912010View commit details
Commits on Jun 19, 2022
-
Configuration menu - View commit details
-
Copy full SHA for a9fc359 - Browse repository at this point
Copy the full SHA a9fc359View commit details -
Configuration menu - View commit details
-
Copy full SHA for 04953ce - Browse repository at this point
Copy the full SHA 04953ceView commit details -
Configuration menu - View commit details
-
Copy full SHA for fe27416 - Browse repository at this point
Copy the full SHA fe27416View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7a1a518 - Browse repository at this point
Copy the full SHA 7a1a518View commit details -
Configuration menu - View commit details
-
Copy full SHA for b0c50be - Browse repository at this point
Copy the full SHA b0c50beView commit details -
Configuration menu - View commit details
-
Copy full SHA for eb1f011 - Browse repository at this point
Copy the full SHA eb1f011View 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 main...typed-headers