From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx-relay34-hz1.antispameurope.com (mx-relay34-hz1.antispameurope.com [94.100.133.210]) by server2.sourceware.org (Postfix) with ESMTPS id 8CF5E385E82C for ; Sun, 8 Mar 2020 10:13:49 +0000 (GMT) Received: from s041.bre.qsc.de ([195.90.7.81]) by mx-relay34-hz1.antispameurope.com; Sun, 08 Mar 2020 11:13:47 +0100 Received: from localhost.localdomain (port-92-195-179-174.dynamic.as20676.net [92.195.179.174]) by s041.bre.qsc.de (Postfix) with ESMTPSA id B77042C03CB; Sun, 8 Mar 2020 11:13:45 +0100 (CET) Subject: =?UTF-8?Q?Re=3a_GCC_server_=e2=80=93_mailing_archive=27s_/current_n?= =?UTF-8?Q?o_longer_working?= To: overseers@gcc.gnu.org, Gerald Pfeifer References: <5ea64eff-45a4-b86b-a168-362c8645060c@net-b.de> <20200307195928.GA9718@cgf.cx> From: Tobias Burnus Message-ID: Date: Sun, 8 Mar 2020 11:13:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <20200307195928.GA9718@cgf.cx> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-cloud-security-sender: burnus@net-b.de X-cloud-security-recipient: overseers@gcc.gnu.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mx-relay34-hz1.antispameurope.com with 26FEB1C1520 X-cloud-security-connect: s041.bre.qsc.de[195.90.7.81], TLS=1, IP=195.90.7.81 X-cloud-security: scantime:.2212 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2020 10:13:50 -0000 Hi, how about simply redirecting "/ml//current" to "/pipermail/"? This avoids the not-found issue and one ends up at the new mailing archive (albeit not for the current month, but that's way better than an error message). Cheers, Tobias On 3/7/20 8:59 PM, Christopher Faylor wrote: > On Sat, Mar 07, 2020 at 07:25:44PM +0100, Tobias Burnus wrote: >> I don't know whether this due to the move to the new server, but the >> "current" links to the current month does no longer work: >> >> https://gcc.gnu.org/ml/gcc-patches/current shows not found but should >> re-direct (this month) to https://gcc.gnu.org/ml/gcc-patches/2020-03/ >> as always working and as documented under https://gcc.gnu.org/ml/ > We're using mailman now so the "current" link no longer works. The /ml/ > directory is currently only for legacy mailing lists. Mailman puts the > archives in, e.g., https://gcc.gnu.org/pipermail/gcc-patches/ . > > I'm thinking about ways to merge the old and new archives but, for now, > you must use the /pipermail/ link to access archives in the new > sourceware. > > cgf >