From: Carlos O'Donell <codonell@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, info-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Thu, 28 Nov 2019 15:45:00 -0000 [thread overview]
Message-ID: <f8535905-2836-1279-a76e-412daae2796c@redhat.com> (raw)
In-Reply-To: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org>
On 11/28/19 12:00 AM, Siddhesh Poyarekar wrote:
> Hi,
>
> During discussions over patch tracking systems on the glibc libc-alpha
> mailing list[1] we thought it would be a worthwhile experiment to try
> the latest patchwork to see if it fits our needs. A quick look through
> the current instance on patchwork.sourceware.org indicates that none of
> the current projects (glibc, gdb, guix) are actively using the instance,
> so I will be nuking it and reinstalling it afresh.
>
> I intend to do this during the day of 1 Dec 2019, India time, so if
> there are any objections or if you would like to take backups, please do
> so before that.
I have no objection to nuking the entire state.
My only use of patchwork was to review old patches for a particular
subsystem. So for example when we were working on malloc changes I would
review what was in the backlog and do an update of all those bugs.
This was just a courtesy to users who had posted previous patches that
we'd never gotten around to fixing. I could do a similar query by just
looking back across the mailing list and grepping for "malloc" or
similar.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-11-28 15:45 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
2019-11-28 15:45 ` Carlos O'Donell [this message]
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=f8535905-2836-1279-a76e-412daae2796c@redhat.com \
--to=codonell@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=info-guix@gnu.org \
--cc=libc-alpha@sourceware.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).