Add more documentation about the RFC 2822 obsolete date format #1267
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pitdicker
force-pushed
the
rfc2822_obsolete_format
branch
from
86ad125
to
674ad9e
Compare
Codecov Report
@@ Coverage Diff @@
## 0.4.x #1267 +/- ##
==========================================
- Coverage 91.40% 91.40% -0.01%
==========================================
Files 38 38
Lines 16933 16932 -1
==========================================
- Hits 15478 15477 -1
Misses 1455 1455
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
djc
approved these changes
Sep 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had some notes about the relation between RFC 822, RFC 2822 and RFC 5322, and why single-letter timezones no longer carry a meaning.