From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58047 invoked by alias); 28 Nov 2019 15:45:37 -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 57938 invoked by uid 89); 28 Nov 2019 15:45:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 spammy=subsystem, our, day X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-2.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (205.139.110.61) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Nov 2019 15:45:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574955904; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XAm00Crsmk9VCAV+87VpUyxpwSLBUBf7Lwgt9Z7AXEw=; b=ORogKO7BHB9hIi3jjiHMAqpA87lDirlUqLQXb+ZXsKXPKXiMn/+Vue3skrJb5KgO6Ckt3U O9q5Cu6I1iTpBpa2RhrE+r94O2BVRw5OeR74+QG9VmscRTMDiic7DDqCyJ/hWZDwJ4N0l4 dYxOyWIIe3DDvD1x0YGRAnd/U0YOf4w= Received: from mail-qv1-f69.google.com (mail-qv1-f69.google.com [209.85.219.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-310-ONaADgrNOWSLvsq584UYKQ-1; Thu, 28 Nov 2019 10:45:03 -0500 Received: by mail-qv1-f69.google.com with SMTP id g9so13862116qvx.12 for ; Thu, 28 Nov 2019 07:45:03 -0800 (PST) Return-Path: Received: from [192.168.1.4] (135-23-175-75.cpe.pppoe.ca. [135.23.175.75]) by smtp.gmail.com with ESMTPSA id n32sm4681498qtk.66.2019.11.28.07.45.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Nov 2019 07:45:02 -0800 (PST) Subject: Re: [X-POST] patchwork.sourceware.org refresh To: Siddhesh Poyarekar , GLIBC Devel , gdb-patches@sourceware.org, info-guix@gnu.org References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> From: Carlos O'Donell Message-ID: Date: Thu, 28 Nov 2019 15:45:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-11/txt/msg01107.txt.bz2 On 11/28/19 12:00 AM, Siddhesh Poyarekar wrote: > Hi, > > 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. > > 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. I have no objection to nuking the entire state. My only use of patchwork was to review old patches for a particular subsystem. So for example when we were working on malloc changes I would review what was in the backlog and do an update of all those bugs. This was just a courtesy to users who had posted previous patches that we'd never gotten around to fixing. I could do a similar query by just looking back across the mailing list and grepping for "malloc" or similar. -- Cheers, Carlos.