From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 6AF0E1F463 for ; Thu, 28 Nov 2019 05:25:31 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=sh6Un CI35Z6eQDc8JrXeTgm/91yTIGbWtpoot4SFbqVLlUsl3xqVpRJ5KtuR7TozaA0jT KPGeBPRY1U1TjnZpj8AX5KYT0oP05XNUfnX60d2znu5JKiZTyYhZ8UkfcaaBDlKq P6oAIv92R/JfFZjnUleOqdT/vQvjWw9yBQwvac= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=qrEjJZhlPH3 0+DZvwyshk8LfZrw=; b=yBKwJg1qY0zSRzfrn40lJGzg0zZRR0kj0emFMumnL7p lap5IRxmnPq6kcaNeY8JJWTv2ntQ2IqOREQX4mRr2LLkLOsUsHWEyi2C/iu3KYhR 2wpvbpPuog36vFSBJaumnT/o5bZdOBEt3o4obNybWJR6+CyJdvlt2JU3alM3L8S8 = 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-Unsubscribe: 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-HELO: cvs.linux-mips.org Date: Thu, 28 Nov 2019 05:25:24 +0000 (GMT) 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 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