From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.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: Mon, 09 Dec 2019 15:44:00 -0000 [thread overview]
Message-ID: <87tv698px0.fsf@redhat.com> (raw)
In-Reply-To: <d6b8afad-7c98-c23f-aca9-e81072ecdfe4@gotplt.org> (Siddhesh Poyarekar's message of "Sun, 8 Dec 2019 17:36:55 +0530")
On Sunday, December 08 2019, Siddhesh Poyarekar wrote:
> Hello,
>
> 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.
Hey, Siddhesh,
I know you're in touch with Konstantin already, but another option would
be to use the OSCI VM running on gnutoolchain-gerrit.osci.io. I can
talk to the OSCI folks and ask them if it'd be possible to have an alias
hostname or something to make it easier to separate the services, if needed.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-12-09 15:44 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
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 [this message]
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=87tv698px0.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=help-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).