From: Carlos O'Donell <codonell@redhat.com>
To: Tom Tromey <tom@tromey.com>, Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Wed, 04 Dec 2019 01:06:00 -0000 [thread overview]
Message-ID: <4dc01c09-74e9-c7b9-e07f-20931ffd12ce@redhat.com> (raw)
In-Reply-To: <87fti1cjor.fsf@tromey.com>
On 12/3/19 2:07 PM, Tom Tromey wrote:
>>>>>> "Siddhesh" == Siddhesh Poyarekar <siddhesh@gotplt.org> 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.
next prev parent reply other threads:[~2019-12-04 1:06 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
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 [this message]
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 ` Florian Weimer
2019-11-29 12:52 ` Andrew Burgess
2019-11-29 13:24 ` Florian Weimer
2019-11-28 16:24 ` Carlos O'Donell
2019-11-28 16:45 ` Siddhesh Poyarekar
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=4dc01c09-74e9-c7b9-e07f-20931ffd12ce@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 \
--cc=tom@tromey.com \
/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).