From: Christian Biesinger <cbiesinger@google.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches <gdb-patches@sourceware.org>,
help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Tue, 14 Jan 2020 14:05:36 -0500 [thread overview]
Message-ID: <CAPTJ0XEmDFBSRhabGx6YoM=R8H9YxxY3tsc1i6Mi_=Eg_fcq6g@mail.gmail.com> (raw)
In-Reply-To: <87pngx8lok.fsf@redhat.com>
On Mon, Dec 9, 2019 at 12:16 PM Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
>
> On Monday, December 09 2019, Siddhesh Poyarekar wrote:
>
> > On 09/12/19 9:14 pm, Sergio Durigan Junior wrote:
> >> 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.
> >
> > That works too, since Konstantin just confirmed that they cannot host
> > this on kernel.org.
>
> Alright. I'll get in touch with OSCI. Please send me your public SSH
> key so I can give you access to the machine.
Any news on this upgrade? Would be nice to play with patchwork for gdb.
Christian
next prev parent reply other threads:[~2020-01-14 19:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 5:00 [X-POST] patchwork.sourceware.org refresh 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:26 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:05 ` Carlos O'Donell
2019-11-28 15:45 ` Carlos O'Donell
2019-11-28 16:02 ` Florian Weimer
2019-11-28 16:09 ` Siddhesh Poyarekar
2019-11-28 16:23 ` 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:44 ` Siddhesh Poyarekar
2019-12-08 12:06 ` 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 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 [this message]
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPTJ0XEmDFBSRhabGx6YoM=R8H9YxxY3tsc1i6Mi_=Eg_fcq6g@mail.gmail.com' \
--to=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=help-guix@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=sergiodj@redhat.com \
--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).