From: Christian Brauner <christian.brauner@ubuntu.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, help-guix@gnu.org,
konstantin@linuxfoundation.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Sun, 8 Dec 2019 13:21:17 +0100 [thread overview]
Message-ID: <20191208122116.ae5wl4eytedt54vg@wittgenstein> (raw)
In-Reply-To: <87y2vnxbk2.fsf@mid.deneb.enyo.de>
On Sun, Dec 08, 2019 at 01:10:37PM +0100, Florian Weimer wrote:
> * Siddhesh Poyarekar:
>
> > I've been battling with this on and off for a couple of weeks now and
> > I've finally given up because I haven't been able to get the
> > dependencies in order for the latest patchwork+django on the sourceware
> > server.
> >
> > I can bring patchwork.siddhesh.in (that thing i set up before moving to
> > patchwork.sourceware.org) back up to the latest with data from
> > patchwork.sourceware.org. Would that work for people wanting to try
> > this out? We can migrate back to patchwork.sourceware.org once it is
> > ready for the latest patchwork.
>
> Maybe we can use <https://patchwork.kernel.org/> for temporary
> hosting? It already covers some non-kernel lists.
If this is an option you'd probably need to talk to Konstantin about
this.
Christian
next prev parent reply other threads:[~2019-12-08 12:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org>
2019-11-28 5:04 ` Fwd: [X-POST] patchwork.sourceware.org refresh Siddhesh Poyarekar
[not found] ` <alpine.LFD.2.21.1911280509420.3472978@eddie.linux-mips.org>
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:26 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:05 ` Carlos O'Donell
2019-12-08 12:06 ` Siddhesh Poyarekar
2019-12-08 12:10 ` Florian Weimer
2019-12-08 12:21 ` Christian Brauner [this message]
2019-12-09 7:56 ` Siddhesh Poyarekar
2019-12-09 16:52 ` Konstantin Ryabitsev
2019-12-09 16:59 ` Siddhesh Poyarekar
2019-12-09 15:44 ` Sergio Durigan Junior
2019-12-09 16:56 ` Siddhesh Poyarekar
2019-12-09 17:15 ` Sergio Durigan Junior
2020-01-14 19:05 ` Christian Biesinger
2020-01-15 2:33 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191208122116.ae5wl4eytedt54vg@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=fw@deneb.enyo.de \
--cc=gdb-patches@sourceware.org \
--cc=help-guix@gnu.org \
--cc=konstantin@linuxfoundation.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).