From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19632 invoked by alias); 4 Dec 2019 01:06:06 -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 19624 invoked by uid 89); 4 Dec 2019 01:06:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*i:sk:87fti1c, H*f:sk:87fti1c, H*MI:sk:87fti1c X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-1.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Dec 2019 01:06:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575421562; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hcJxqumZVhIfsntMbONOMZSGFTyOOWpP65nC0O0UlxY=; b=UwZmw6UMIuBCwUTsAa2tPt3ese3Vnk7cKxQhM1TZfRPUQGUj65+JrhX5cocProjmKnAn2C U1oGl5x6N7BR8vo1E2G6A0YjzlhVxNYTJYkSB+hDba8EW94yxgZdu1Ol0anYNR6No3rSJ7 nEb3UYPy8ncW6J94OoNTEADe14vnFbI= Received: from mail-qv1-f71.google.com (mail-qv1-f71.google.com [209.85.219.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-209-w78rzstJNDqn44DwmL4ROA-1; Tue, 03 Dec 2019 20:06:02 -0500 Received: by mail-qv1-f71.google.com with SMTP id d12so3471791qvj.16 for ; Tue, 03 Dec 2019 17:06:02 -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 63sm2765329qki.57.2019.12.03.17.05.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Dec 2019 17:06:00 -0800 (PST) Subject: Re: [X-POST] patchwork.sourceware.org refresh To: Tom Tromey , Siddhesh Poyarekar Cc: "Maciej W. Rozycki" , GLIBC Devel , gdb-patches@sourceware.org, help-guix@gnu.org References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org> <87fti1cjor.fsf@tromey.com> From: Carlos O'Donell Message-ID: <4dc01c09-74e9-c7b9-e07f-20931ffd12ce@redhat.com> Date: Wed, 04 Dec 2019 01:06: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: <87fti1cjor.fsf@tromey.com> X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00109.txt.bz2 On 12/3/19 2:07 PM, Tom Tromey wrote: >>>>>> "Siddhesh" == Siddhesh Poyarekar writes: > >>> Or do you have something else, i.e. not just an upgrade, in mind? > > Siddhesh> To begin with, I intend to add hooks to close patchwork patches on merge > Siddhesh> so that that aspect is automated. It was the one problem we had with > Siddhesh> patchwork and with ChangeLogs gone in glibc, we're definitely a lot more > Siddhesh> likely to get close to that goal. > > For gdb, I'd like this to be much more reliable than it is today. We > were thinking we'd simply add a kind of patch-id to the commit message > -- the way we're currently doing with gerrit -- and then have patchworks > recognize this ID and use it as its internal key. > > I think this is not a very large amount of work in patchworks. That would be awesome. -- Cheers, Carlos.