From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 C424A21B02822 for ; Mon, 25 Mar 2019 05:51:18 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 69E7430BC661; Mon, 25 Mar 2019 12:51:17 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-188.rdu2.redhat.com [10.10.120.188]) by smtp.corp.redhat.com (Postfix) with ESMTP id BF8BB601AC; Mon, 25 Mar 2019 12:51:16 +0000 (UTC) To: stephano , "edk2-devel@lists.01.org" References: From: Laszlo Ersek Message-ID: Date: Mon, 25 Mar 2019 13:51:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Mon, 25 Mar 2019 12:51:17 +0000 (UTC) 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 12:51:19 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Hi Stephano, On 03/23/19 01:41, stephano wrote: > I will be moving our mailing list from 01.org over to Groups.io as of > April 4th. I will send out another warning 1 week before, and a final > warning 1 day before the move. > > On April 4th the edk2-devel@lists.01.org will begin to bounce emails and > I will begin uploading the archive to Groups.io. I do not have an > estimate from Groups.io on how long that archive upload will take. > > To summarize: after April 4th 2019 you can *no longer send patches to > edk2-devel@lists.01.org*. Please send all patches to: > > devel@edk2.groups.io Can you please confirm that the current mailing list archive URLs will continue working? For example: https://lists.01.org/pipermail/edk2-devel/2019-March/038114.html It's fine if the archive will not be extended with new messages in the future, and also if the old messages get uploaded in the new list archive. However, the old links should continue working as well, indefinitely (it will not require additional storage, just a bit of additional bandwidth, as old messages are looked up). 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. *However*, that's just me. Most people include just one link, and that's into the current master archive. Those links make no sense outside of the specific archive service. And, I suffer *to this day* from the fact that GMANE had gone down in summer 2016, and a huge amount of old references (into the GMANE archive) are now completely useless. In brief, please preseve the archive at , albeit with locked down content, indefinitely. Thank you, Laszlo > > This new list requires 1 email approval before you can post, so please > be patient as our moderators approve you all. > > After April 4th, all announcements will come from: > > announce@edk2.groups.io > > This list only allows moderators to post, so please contact me if you > have announcements. > > As always, I welcome your comments and questions. Thank you for your > patience while we work to improve the quality of our community. > > Cheers, > Stephano > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel