-
Notifications
You must be signed in to change notification settings - Fork 205
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
Testing notifications to quic-issues@ietf.org #4
Labels
editorial
An issue that does not affect the design of the protocol; does not require consensus.
Comments
Matt says things are fixed; testing |
Testing base drafts, sorry for the spam. |
Seeing if a settings change makes GitHub not use BCC when it sends notifications. @mattinfla: check the logs, too, please? |
It seems as if this settings change has fixed notifications. Fingers crossed. |
mnot
added
the
editorial
An issue that does not affect the design of the protocol; does not require consensus.
label
Apr 19, 2017
siyengar
pushed a commit
to siyengar/base-drafts
that referenced
this issue
May 17, 2018
Fix some typos in loss recovery
martinthomson
pushed a commit
that referenced
this issue
Dec 12, 2019
Move alternative confirmation method
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
editorial
An issue that does not affect the design of the protocol; does not require consensus.
Sorry for the spam. We only seem to get issue notifications through intermittently.
The text was updated successfully, but these errors were encountered: