IETF Logo Mail Archive

Re: [quicwg/base-drafts] Describe the two processes. (9f6e285)

ianswett <notifications@github.com> Mon, 11 February 2019 15:23 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED0C126F72 for <quic-issues@ietfa.amsl.com>; Mon, 11 Feb 2019 07:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6WfYjsCHCFes for <quic-issues@ietfa.amsl.com>; Mon, 11 Feb 2019 07:23:08 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B434A130ECE for <quic-issues@ietf.org>; Mon, 11 Feb 2019 07:23:07 -0800 (PST)
Date: Mon, 11 Feb 2019 07:23:06 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549898586; bh=loOB2XUOy59/zsYwBrwTD7nb7WFfUPz2KsqeTV9Xdn8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=i6YnMOjTB977tscosh8riqx2unAXQfVwoXcgaCPrFkeiAaPlOZu/86Tg1nFzT2WTp zaiMFwNc64hvasJ3lP/UCjoz57eTOPYqWIk5ZWVQ0qVq04P8Yk3/fRf9xoKyVV/GP5 1DUuKqyR/6kLoqLLE40tDJcYUOF9qy7Pxh1mgrT8=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8a5e8f0fbc63e6eff465a22b70413591319c8f9392cf000000011879555a92a163ce01ec66b4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/commit/9f6e285ad51c3439d5abd0ba24ad4ecd081c7a25/32270004@github.com>
In-Reply-To: <quicwg/base-drafts/commit/9f6e285ad51c3439d5abd0ba24ad4ecd081c7a25@github.com>
References: <quicwg/base-drafts/commit/9f6e285ad51c3439d5abd0ba24ad4ecd081c7a25@github.com>
Subject: Re: [quicwg/base-drafts] Describe the two processes. (9f6e285)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c61935aa557e_58553ffabcad45c0682941"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VHIyWY64Ofs96eo4T35dEFmOWSk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2019 15:23:11 -0000

Are you saying that an issue could be closed, but no have consensus, and that would be indicated by a lack of the 'has-consensus' flag?  If so, that's confusing to me, since most closed issues at the moment aren't marked 'has-consensus'.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/commit/9f6e285ad51c3439d5abd0ba24ad4ecd081c7a25#commitcomment-32270004

v2.14.0 | Report a Bug | By Email