From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id fD6TLQfol2PrJicAWB0awg (envelope-from ) for ; Mon, 12 Dec 2022 21:48:39 -0500 Received: by simark.ca (Postfix, from userid 112) id AC3611E124; Mon, 12 Dec 2022 21:48:39 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=bkK/SBNk; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 64A371E0CB for ; Mon, 12 Dec 2022 21:48:39 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id AF75C384698F for ; Tue, 13 Dec 2022 02:48:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AF75C384698F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670899718; bh=Bf2j6xkvhbXKecC5h8U6nVWImcdLnDkEHB4Tx39ULgc=; h=To:Cc:Subject:References:Date:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=bkK/SBNk/PfNbFpG2Hv3OvOlOCWVdFUli/1TqXehGeWu3I4+X6C0bB+cb+JgeRrod LnyKt9YJeFwa1yumJKmgLh61Q1s/qZ6L2uHe7KL5ox281QapMLGSu9EHDbn6mID/d3 Aq3edTb28BnSDWtLVt47raexpPOEWpGiXAzMNVvM= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 1A51238475B6 for ; Tue, 13 Dec 2022 02:48:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1A51238475B6 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-656-t8r0quqdNoK-856mGx4Xew-1; Mon, 12 Dec 2022 21:48:08 -0500 X-MC-Unique: t8r0quqdNoK-856mGx4Xew-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4C38A801580; Tue, 13 Dec 2022 02:48:08 +0000 (UTC) Received: from redhat.com (unknown [10.2.16.56]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 26BC5492B00; Tue, 13 Dec 2022 02:48:08 +0000 (UTC) Received: from [127.0.0.1] (helo=vm-rhel7) by redhat.com with esmtp (Exim 4.94.2) (envelope-from ) id 1p4vKs-0002u0-Jt; Mon, 12 Dec 2022 21:48:03 -0500 To: Luis Machado Cc: "gdb\@sourceware.org" Subject: Re: Any concrete plans after the GDB BoF? References: <83485199-965e-7ff5-1dc8-d027b74b56f7@arm.com> Date: Mon, 12 Dec 2022 21:48:02 -0500 In-Reply-To: <83485199-965e-7ff5-1dc8-d027b74b56f7@arm.com> (Luis Machado via Gdb's message of "Thu, 27 Oct 2022 11:47:56 +0100") Message-ID: <87a63sf28t.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Frank Ch. Eigler via Gdb" Reply-To: "Frank Ch. Eigler" Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Luis Machado via Gdb writes: > [...] > Simon was kind enough to cleanup the patchworks instance, though that > is not yet fully integrated into > something we can easily use to do tests/CI. I see the number of > unreviewed patches is growing again. Note that gdb maintainers can push hypothetical patches to personal try-branches on sourceware.org ("git push origin users/$USERID/try-TOPIC"), and the local buildbot environment will build that branch on a variety of hosts, report build failures, and store test results in bunsen. This is not integrated into patchwork, but is easily triggered by anyone with commit privileges. - FChE