Re: [X-POST] patchwork.sourceware.org refresh

Maciej W. Rozycki
2019-11-28T05:25:29Z

On Thu, 28 Nov 2019, Siddhesh Poyarekar wrote:

> 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.

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).

> 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.

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.

Or do you have something else, i.e. not just an upgrade, in mind?

Maciej