From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.1 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 44F301F463 for ; Mon, 9 Dec 2019 07:56:56 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=vf2+aJTLmQ+8YWq7 V2YFIFshEE92mpy1ZHIl5SEbDXxn974dkVaWnGNY3O1VfXE1K2AEwnbxfAi2uZP7 hSyyIjK68YcDxjW+/v6EeceBOPovrAZW813wV1FPA/NQ7nXNxLRVaeQwcTCEM5K9 GuomSpOBhN0PwvjeQ3BVZrySNZQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=ZB10A7mREDXjfymLwHYeJG DZxXo=; b=gSWZVUz2k0Z/kAgG9KCJRMVDpSZi5b0GIweEP4Uf3koI1sNaOTyA4G venISgILUasbSPFX1IgK3IqiE7P2qejCg6qeiY24KUgAhqxrhYnFw8yB9IMw5o1f OT2Vvr3OwR+KegC2piS0JPxyBmkS2aPDyLgSjhg3xSzSRY4duHtbM= Received: (qmail 128760 invoked by alias); 9 Dec 2019 07:56:53 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 128741 invoked by uid 89); 9 Dec 2019 07:56:53 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: crocodile.birch.relay.mailchannels.net X-Sender-Id: dreamhost|x-authsender|siddhesh@gotplt.org X-Sender-Id: dreamhost|x-authsender|siddhesh@gotplt.org X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|siddhesh@gotplt.org X-MailChannels-Auth-Id: dreamhost X-Slimy-Suffer: 6d17a5a40bcc82de_1575878208250_2107987872 X-MC-Loop-Signature: 1575878208250:1939908522 X-MC-Ingress-Time: 1575878208250 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gotplt.org; h=subject:to :cc:references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=gotplt.org; bh=ZB10A7 mREDXjfymLwHYeJGDZxXo=; b=BKMQQSeHAP101rwVh67C0ShyU2qbK8xviCGv2w JS5MyQxNR3LJwUX5Ucvw+tR1/luv9698hgUJdSIcjQ90xuRDKth7hjTb+STsXQA9 OBCX48pCU/4ClDnvtC0gz9aHZ3Nzg2vyMhzYoctkI2iRQuH3b2xe35vHDTApPPhI fGYvk= Subject: Re: [X-POST] patchwork.sourceware.org refresh To: Christian Brauner , Florian Weimer Cc: GLIBC Devel , gdb-patches@sourceware.org, help-guix@gnu.org, konstantin@linuxfoundation.org References: <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org> <87y2vnxbk2.fsf@mid.deneb.enyo.de> <20191208122116.ae5wl4eytedt54vg@wittgenstein> X-DH-BACKEND: pdx1-sub0-mail-a82 From: Siddhesh Poyarekar Message-ID: <821c81bd-3c9a-0d33-ffbe-924de796dc7e@gotplt.org> Date: Mon, 9 Dec 2019 13:26:16 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: <20191208122116.ae5wl4eytedt54vg@wittgenstein> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 08/12/19 5:51 pm, Christian Brauner wrote: >> Maybe we can use 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