From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=134.134.136.100; helo=mga07.intel.com; envelope-from=stephano.cetola@linux.intel.com; receiver=edk2-devel@lists.01.org Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8589521B02822 for ; Mon, 25 Mar 2019 09:21:33 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Mar 2019 09:21:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,269,1549958400"; d="scan'208";a="285749363" Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.251.158.163]) ([10.251.158.163]) by orsmga004.jf.intel.com with ESMTP; 25 Mar 2019 09:21:25 -0700 To: Laszlo Ersek References: Cc: "edk2-devel@lists.01.org" From: stephano Message-ID: <520cc50a-bb52-d24e-4c73-eb8cd8b0a312@linux.intel.com> Date: Mon, 25 Mar 2019 09:21:25 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: [edk2-announce] Mailing List Move Day Set: April 4th X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2019 16:21:33 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit On 3/25/2019 5:51 AM, Laszlo Ersek wrote: > Hi Stephano, > > Can you please confirm that the current mailing list archive URLs will > continue working? Yes, I'll check on this today. > Personally, when I provide archive links (in discussions, BZs, commit > messages etc), I tend to make sure that I include two links: one into > the master archive, and another (to the same message) into the > mail-archive.com archive. From these, I make sure that the 2nd one is > always a Message-ID-based URL. The benefit is that, even if > mail-archive.com disappears, people can construct new URLs to old > messages, from the old message-IDs that are captured in the old URLs -- > assuming a new archive service exposes the old messages by message-ID again. This is a good point and shows the level of detail that is preserved by the mailing list if maintained properly. I would assume this is part of the reason that the Linux kernel has continued to use mailing lists for patch review as this level of detail is highly desired in their case. > In brief, please preseve the archive at > , albeit with locked down > content, indefinitely. Will do. Cheers, Stephano