From: Carlos O'Donell <codonell@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Thu, 28 Nov 2019 15:47:00 -0000 [thread overview]
Message-ID: <30104df7-d224-0b62-5e95-22ced08659f1@redhat.com> (raw)
In-Reply-To: <1277b1bb-c3c4-6fc8-a700-c7207efd31cf@gotplt.org>
On 11/28/19 12:47 AM, Siddhesh Poyarekar wrote:
> 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.
When I looked at this the upgrade was *very* complicated, and carrying over
the data from a version that is so old was going to be hard.
>> 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.
Agreed!
For me as a reviewer, knowing what's up-to-date and ready for review,
having a tool (like pwclient) to pull the patch and build a local branch
from it, and then being able to use local diff tooling is really the key
things to accelerate patch review for patches that don't require complex
consensus.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-11-28 15:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 5:01 Siddhesh Poyarekar
2019-11-28 5:11 ` Simon Marchi
2019-11-28 5:25 ` Maciej W. Rozycki
2019-11-28 5:47 ` Siddhesh Poyarekar
2019-11-28 15:47 ` Carlos O'Donell [this message]
2019-11-30 11:35 ` Maciej W. Rozycki
2019-12-01 4:35 ` Siddhesh Poyarekar
2019-12-01 16:27 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:06 ` Carlos O'Donell
2019-11-28 15:45 ` Carlos O'Donell
2019-11-28 16:03 ` Florian Weimer
2019-11-28 16:09 ` Siddhesh Poyarekar
2019-11-28 16:24 ` Carlos O'Donell
2019-11-28 16:45 ` Siddhesh Poyarekar
2019-11-28 16:24 ` Florian Weimer
2019-11-29 12:52 ` Andrew Burgess
2019-11-29 13:24 ` Florian Weimer
2019-12-08 12:07 ` Siddhesh Poyarekar
2019-12-08 12:10 ` Florian Weimer
2019-12-08 12:21 ` Christian Brauner
2019-12-09 7:56 ` Siddhesh Poyarekar
2019-12-09 16:52 ` Konstantin Ryabitsev
2019-12-09 17:00 ` Siddhesh Poyarekar
2019-12-09 15:44 ` Sergio Durigan Junior
2019-12-09 16:57 ` Siddhesh Poyarekar
2019-12-09 17:15 ` Sergio Durigan Junior
2020-01-14 19:06 ` Christian Biesinger
2020-01-15 2:34 ` Siddhesh Poyarekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30104df7-d224-0b62-5e95-22ced08659f1@redhat.com \
--to=codonell@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=help-guix@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=macro@linux-mips.org \
--cc=siddhesh@gotplt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).