Re: Adjustments to our work mode - please read

Mark Nottingham <> Wed, 07 October 2015 06:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id C12FC1A873B for <>; Tue, 6 Oct 2015 23:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8M9p-Z3dKqII for <>; Tue, 6 Oct 2015 23:59:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1A2501A8749 for <>; Tue, 6 Oct 2015 23:59:20 -0700 (PDT)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1Zjidp-0008Kh-5c for; Wed, 07 Oct 2015 06:55:57 +0000
Resent-Date: Wed, 07 Oct 2015 06:55:57 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1Zjidm-0008Jv-9z for; Wed, 07 Oct 2015 06:55:54 +0000
Received: from ([]) by with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <>) id 1Zjidj-0008B7-PU for; Wed, 07 Oct 2015 06:55:53 +0000
Received: from [] (unknown []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id AB6A922E25F; Wed, 7 Oct 2015 02:55:05 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Mark Nottingham <>
In-Reply-To: <>
Date: Wed, 07 Oct 2015 17:55:02 +1100
Cc: Brian Smith <>, HTTP Working Group <>, Barry Leiba <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Ted Hardie <>
X-Mailer: Apple Mail (2.2104)
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-8.2
X-W3C-Hub-Spam-Report: AWL=1.365, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: 1Zjidj-0008B7-PU 116eb67f1bb48afe4d12b925a525ed5f
Subject: Re: Adjustments to our work mode - please read
Archived-At: <>
X-Mailing-List: <> archive/latest/30342
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

Hi Ted,

I think you're talking about the first one, which was pushed out by the [http-issues] prefix. I've since removed that, reducing the likelihood of this happening.

Also, that appears to be only an artefact of the Web interface, not the e-mail list itself.


> On 7 Oct 2015, at 3:18 am, Ted Hardie <> wrote:
> On Mon, Oct 5, 2015 at 4:43 PM, Brian Smith <> wrote:
> - Provide a separate, announce-only mailing list that is subscribed to every issue change, for those who do not want to use a github account to receive notifications. See: <>
> Note that GitHub comments can be edited and deleted after the fact, so it is very important that the http-issues list be a reliable archive of all the communication.
> ​Brian's comment caused me to go look at the archive, which is found here:
> There is a bit of a problem using the new mailing list archive system with the current method. As it stands, the mailing list archive truncates the subject of the email after a certain point (apparently no matter what the width of the window it won't go beyond a certain number of characters).  Because the issue numbers come at the end of the line, the issue number drops off.  This is already visible in the archive, even though there are only three messages.
> Any chance we can massage github to move the issue numbers to the front?  
> Also, it was not entirely clear to me from the headers whether the mailing list archive system threading will work correctly with these messages.  By any chance, did you test that with another list?
> regards,
> Ted

Mark Nottingham