From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Tromey Subject: Re: [X-POST] patchwork.sourceware.org refresh Date: Tue, 03 Dec 2019 12:07:00 -0700 Message-ID: <87fti1cjor.fsf@tromey.com> References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org> (Siddhesh Poyarekar's message of "Thu, 28 Nov 2019 11:17:16 +0530") To: Siddhesh Poyarekar Cc: "Maciej W. Rozycki" , GLIBC Devel , gdb-patches@sourceware.org, help-guix@gnu.org List-Id: help-guix.gnu.org >>>>> "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. Tom