unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Christian Brauner <christian.brauner@ubuntu.com>,
	Florian Weimer <fw@deneb.enyo.de>
Cc: 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: Mon, 9 Dec 2019 13:26:16 +0530	[thread overview]
Message-ID: <821c81bd-3c9a-0d33-ffbe-924de796dc7e@gotplt.org> (raw)
In-Reply-To: <20191208122116.ae5wl4eytedt54vg@wittgenstein>

On 08/12/19 5:51 pm, Christian Brauner wrote:
>> 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.

Oh of course, less work is always better, I was only trying not to
bother them since we had not finalized use of patchwork.  Konstantin if
you're OK with us using the patchwork.kernel.org instance as a pilot,
it'll be great if you could set up an instance for glibc.

I had a couple of questions though before we set this up because these
were points that led to bitrot in our patchwork instance:

1. Do you have hooks in place to auto-close patches in patchwork when
they're committed?

2. Do you know if patchwork reliably closes off older versions of patch
submissions, or if there's a way other projects are managing this.

3. Could you allow one of us (me to start with) to add hooks to do CI
runs?  Alternatively, do you have some CI infrastructure in place that
allows projects to do builds against a patchwork submission and report
errors to the mailing list?

These are things I was going to explore with a local patchwork instance
and if it's possible with patchwork.kernel.org, I'm all for it.

Thanks,
Siddhesh

  reply	other threads:[~2019-12-09  7:56 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 [this message]
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://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=821c81bd-3c9a-0d33-ffbe-924de796dc7e@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).