Skip to content
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

Closed
larseggert opened this issue Nov 22, 2016 · 4 comments
Closed

Testing notifications to quic-issues@ietf.org #4

larseggert opened this issue Nov 22, 2016 · 4 comments
Labels
editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@larseggert
Copy link
Member

Sorry for the spam. We only seem to get issue notifications through intermittently.

@larseggert
Copy link
Member Author

Matt says things are fixed; testing

@mattinfla
Copy link

Testing base drafts, sorry for the spam.

@quic-issues
Copy link
Member

Seeing if a settings change makes GitHub not use BCC when it sends notifications. @mattinfla: check the logs, too, please?

@larseggert
Copy link
Member Author

It seems as if this settings change has fixed notifications. Fingers crossed.

@mnot mnot added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Apr 19, 2017
martinthomson pushed a commit that referenced this issue Apr 15, 2018
siyengar pushed a commit to siyengar/base-drafts that referenced this issue May 17, 2018
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.
Projects
None yet
Development

No branches or pull requests

4 participants