From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84140 invoked by alias); 28 Nov 2019 05:47:48 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 84116 invoked by uid 89); 28 Nov 2019 05:47:47 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy= X-HELO: antelope.elm.relay.mailchannels.net Received: from antelope.elm.relay.mailchannels.net (HELO antelope.elm.relay.mailchannels.net) (23.83.212.4) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Nov 2019 05:47:45 +0000 X-Sender-Id: dreamhost|x-authsender|siddhesh@gotplt.org Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 40DF974107A; Thu, 28 Nov 2019 05:47:43 +0000 (UTC) Received: from pdx1-sub0-mail-a49.g.dreamhost.com (100-96-45-206.trex.outbound.svc.cluster.local [100.96.45.206]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id BBFC67410C5; Thu, 28 Nov 2019 05:47:42 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|siddhesh@gotplt.org Received: from pdx1-sub0-mail-a49.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Thu, 28 Nov 2019 05:47:43 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|siddhesh@gotplt.org X-MailChannels-Auth-Id: dreamhost X-Harmony-Shade: 63bbdb9126d5b74f_1574920063058_3489277611 X-MC-Loop-Signature: 1574920063057:3040279512 X-MC-Ingress-Time: 1574920063057 Received: from pdx1-sub0-mail-a49.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a49.g.dreamhost.com (Postfix) with ESMTP id 1BF6B8601C; Wed, 27 Nov 2019 21:47:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gotplt.org; h=subject:to :cc:references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=gotplt.org; bh=GYdtcM VJ6SHQCrpckowMdEC+y1Q=; b=EKjDZq2z1JyJUdRHCV3Nqx9lwPQIYEYmP67EyU d4WwjQUMan8jiFb2rbDpL3dEXaPrky2fqG6s0278HmQxmQCMCCNN72AChEaHThv9 ef323EXXeXzkgWR72KncMxXP+Miva6hLkXUQc/XKdstVDL0mwu2tnmL6crct9eoH cum7c= Received: from [192.168.0.107] (unknown [123.252.202.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: siddhesh@gotplt.org) by pdx1-sub0-mail-a49.g.dreamhost.com (Postfix) with ESMTPSA id 6ADA286019; Wed, 27 Nov 2019 21:47:33 -0800 (PST) Subject: Re: [X-POST] patchwork.sourceware.org refresh To: "Maciej W. Rozycki" Cc: GLIBC Devel , gdb-patches@sourceware.org, help-guix@gnu.org References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> X-DH-BACKEND: pdx1-sub0-mail-a49 From: Siddhesh Poyarekar Message-ID: <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org> Date: Thu, 28 Nov 2019 05:47:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-11/txt/msg01093.txt.bz2 On 28/11/19 10:55 am, Maciej W. Rozycki wrote: > 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). Can you please take a snapshot of your state? > 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. Hmm, I will try to do an in-place upgrade without actually deleting anything. I can't promise that it will go well because we'll be upgrading from a very ancient version and I don't know right now if the schema has changed incompatibly. I'll do a backup too FWIW. > Or do you have something else, i.e. not just an upgrade, in mind? To begin with, I intend to add hooks to close patchwork patches on merge so that that aspect is automated. It was the one problem we had with patchwork and with ChangeLogs gone in glibc, we're definitely a lot more likely to get close to that goal. Siddhesh