From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Maciej W. Rozycki" Subject: Re: [X-POST] patchwork.sourceware.org refresh Date: Sat, 30 Nov 2019 11:35:14 +0000 (GMT) Message-ID: References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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> To: Siddhesh Poyarekar Cc: GLIBC Devel , gdb-patches@sourceware.org, help-guix@gnu.org List-Id: help-guix.gnu.org On Thu, 28 Nov 2019, Siddhesh Poyarekar 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? How do I do that though? There doesn't appear to be anything there I could do from my profile page or elsewhere. > > 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. Sure, and greatly appreciated too (I've seen your proposal in the other thread of discussion), but adding hooks is not supposed to affect any existing patchwork state that the lone upgrade puts at risk. Some kind of restructuring could. Maciej