From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64714 invoked by alias); 28 Nov 2019 05:25:29 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 64695 invoked by uid 89); 28 Nov 2019 05:25:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY autolearn=ham version=3.3.1 spammy=H*r:user, peoples, HX-Languages-Length:1284, accounts X-HELO: cvs.linux-mips.org Date: Thu, 28 Nov 2019 05:25:00 -0000 From: "Maciej W. Rozycki" To: Siddhesh Poyarekar cc: GLIBC Devel , gdb-patches@sourceware.org, info-guix@gnu.org Subject: Re: [X-POST] patchwork.sourceware.org refresh In-Reply-To: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> Message-ID: References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SW-Source: 2019-11/txt/msg00964.txt.bz2 On Thu, 28 Nov 2019, Siddhesh Poyarekar wrote: > During discussions over patch tracking systems on the glibc libc-alpha > mailing list[1] we thought it would be a worthwhile experiment to try > the latest patchwork to see if it fits our needs. A quick look through > the current instance on patchwork.sourceware.org indicates that none of > the current projects (glibc, gdb, guix) are actively using the instance, > so I will be nuking it and reinstalling it afresh. Well, I've been using it to track the state my own patches submitted (and during the period of my active MIPS GDB port maintenance also for other people's submissions). > I intend to do this during the day of 1 Dec 2019, India time, so if > there are any objections or if you would like to take backups, please do > so before that. Is it actually necessary to destroy all the recorded state (not only for patches, but also for e-mail accounts linked, which AFAIK cannot be restored once you've lost access to any) just for an engine upgrade? That would be an odd requirement and ISTR at least one of the patchworks I've had an account with to have been seamlessly upgraded at one point. Or do you have something else, i.e. not just an upgrade, in mind? Maciej