Re: [quicwg/base-drafts] Help me fix this problem (#3065)

Mike Bishop <> Tue, 24 September 2019 22:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9619B12086B for <>; Tue, 24 Sep 2019 15:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Lc4oJVTNdUFT for <>; Tue, 24 Sep 2019 15:21:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AC27E12083B for <>; Tue, 24 Sep 2019 15:21:10 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BBA856E1451 for <>; Tue, 24 Sep 2019 15:21:09 -0700 (PDT)
Date: Tue, 24 Sep 2019 15:21:09 -0700
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3065/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Help me fix this problem (#3065)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8a96d5ad202_31843f9e71ecd96c80223"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Sep 2019 22:21:13 -0000

>From [](, emphasis added:
> Before filing a new issue, please consider a few things:
> - Issues should be just that; issues with our deliverables, not proposals, questions or support requests.
> - Please review the issues list to make sure that you aren't filing a duplicate.
> - If you're not sure how to phrase your issue, please ask on the mailing list.
> Issues can also be raised on the Working Group mailing list by clearly marking them as such (e.g., "New Issue" in the Subject: line).
> Be aware that issues might be rephrased, changed in scope, or combined with others, so that the group can focus its efforts. If you feel that such a change loses an important part of your original issue, please bring it up, either in comments or on the list.
> **Off-topic and duplicate issues will be closed without discussion.** Note that comments on individual commits will only be responded to with best effort, and may not be seen.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: