From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
Florian Weimer <fw@deneb.enyo.de>,
GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Mon, 9 Dec 2019 22:29:49 +0530 [thread overview]
Message-ID: <607b04dd-26d2-f049-94cc-660eb5d3fd47@gotplt.org> (raw)
In-Reply-To: <20191209165222.oanyqa7s73gzz6yd@chatter.i7.local>
On 09/12/19 10:22 pm, Konstantin Ryabitsev wrote:
> I'm not sure it makes that much sense to put glibc on
> patchwork.kernel.org. I know we have some non-kernel projects there, but
> they are pretty tiny and were approved largely because they wouldn't
> make much of an impact on kernel.org infra.
>
> The same wouldn't be true for glibc, especially if we're talking bot and
> CI integration. It really needs to stay on its own dedicated
> infrastructure where it can be properly scoped and resourced.
>
> Sorry that I don't have a better answer.
>
I understand, thanks anyway.
Siddhesh
next prev parent reply other threads:[~2019-12-09 17:00 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 [this message]
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://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=607b04dd-26d2-f049-94cc-660eb5d3fd47@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=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 \
/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).