From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ElJ+Nmfs8mb15jUAWB0awg (envelope-from ) for ; Tue, 24 Sep 2024 12:44:23 -0400 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=kLkvlQ74; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id BC7181E353; Tue, 24 Sep 2024 12:44:23 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-11.8 required=5.0 tests=ARC_SIGNED,ARC_VALID, BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI,RCVD_IN_VALIDITY_CERTIFIED,RCVD_IN_VALIDITY_RPBL, RCVD_IN_VALIDITY_SAFE,URIBL_BLOCKED,URIBL_DBL_BLOCKED_OPENDNS autolearn=ham autolearn_force=no version=4.0.0 Received: from server2.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 ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id D7B821E05C for ; Tue, 24 Sep 2024 12:44:22 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 37892385840F for ; Tue, 24 Sep 2024 16:44:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37892385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1727196262; bh=HWFZWXe1ezUO2VR6B7QP4Yk0B4UpOo69KEARzsaPMb0=; h=Date:To:cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=kLkvlQ74MpfAWOG10d+lgwYmLkYbcIMwY05e7s1q8BwGTsS6Y8VpBPsKc8hSQooXG 5t/bVEtdKop5Q47rbqXiYNbsZrwQVZkcj3GD9jt1QBLrbEl7xszO0rQoor8PYPmCa9 d9VsoF2iQwqgQgHEz4l6JWkTRrboD7gEBT/CisDQ= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTP id CF65A3858D35 for ; Tue, 24 Sep 2024 16:43:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CF65A3858D35 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org CF65A3858D35 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1727196212; cv=none; b=lyZLo5q5G9Jy3OPukDV306iWmMcYPUlLume79wFj8CDlBCsZnJODMw+vaF8K0HgzoNOlQ0tK0RLiByitZffNSiiloxDoX6vYFQnoThym+t+RKsmkSgEy2D8TL3XtjxFbrOMrm405ujMSPwtlT0W+/Fco8r6WcuIKpoaedACdGOE= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1727196212; c=relaxed/simple; bh=14l7B7tdfsUCQyGT3oDdYPKiXW2hNeVr6vwgwwimgrM=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=ra27G7395ibjtIDGYM7ZSw2i4Brr39KLkT5Csrp/eII4m7gzRzz2JxfiCNTUcnXD4mSwLYyAprdkcmtlvPLJlBnMArw6AlVJFB9ztdqNBe7rHEpfOzinPqgNOjlOxu68VChzqubFBYFf8q6awBftU1fjuNDEkA9brGeJKW3hWAA= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-484--o2v4Kb2NH-WncKOepRWoQ-1; Tue, 24 Sep 2024 12:43:29 -0400 X-MC-Unique: -o2v4Kb2NH-WncKOepRWoQ-1 Received: by mail-wm1-f71.google.com with SMTP id 5b1f17b1804b1-42cceb06940so40515865e9.0 for ; Tue, 24 Sep 2024 09:43:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727196208; x=1727801008; h=mime-version:references:message-id:in-reply-to:subject:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=HWFZWXe1ezUO2VR6B7QP4Yk0B4UpOo69KEARzsaPMb0=; b=NJFWfq0hrN0wxKYNKGAY8NRHzArN3cFmIkPUG9MeENM+PyZulkDj1Y2PSsCy7K25eD iKlAMWzCv1nQunsHwim0+zAoD6vaf/ngmACpo4qJj30fr3Nppbbck5Vy06DxDkoqrIaq TTbA3OU7i0mhE7GRb3/AoqRb7FV8TsWPLr4RihH/HvHPZagNy0hY1ecihloeNidwmB5y qeCBXStLvoKTlKqyqDSYjctEWbDubRJ+02O1fR3ViAr5RmqS1IOow9vFjYDMz8e7DG7V LFC600nsaQ+iHl2D7C9FUJAoUXX2+C24lhQftLNEcIt3cigaccB9gH9MAk5tWwpfcT57 j8jA== X-Forwarded-Encrypted: i=1; AJvYcCVgnzQC+x/ivJ44KhH2zSKJAyRT7uGvgqgH5l/iEzVeZAxk2uuTRtBZw4SFUA2xy26Y8YE=@sourceware.org X-Gm-Message-State: AOJu0Yxez6tB/JyHpjs9vgwPiRmxfVhtwsx3yplbhN86Udc+vV4Ed/OC KfTZC/5XbWQlKIq9OBqVrqFkNH02t7hFn5zolsL76KkColJJ7BYF5FG8ho1WKFGb7gcjE62WvBN poAq4SjPt/cF+4SALTe5tise/fYiSwuQxHE7gpU3p6127NX1H X-Received: by 2002:a05:600c:5127:b0:42c:b961:c902 with SMTP id 5b1f17b1804b1-42e7abe83a4mr90428135e9.12.1727196207960; Tue, 24 Sep 2024 09:43:27 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFNEPzdTYR1ObKg2dKbawfe2F3UKF7ZhG3mDPXzUGdS1IeRIEul/eVuJhgKY+Uf22OyV9Q7Dw== X-Received: by 2002:a05:600c:5127:b0:42c:b961:c902 with SMTP id 5b1f17b1804b1-42e7abe83a4mr90427955e9.12.1727196207506; Tue, 24 Sep 2024 09:43:27 -0700 (PDT) Received: from digraph.polyomino.org.uk (digraph.polyomino.org.uk. [2001:8b0:bf73:93f7::51bb:e332]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-42e84f24416sm98883145e9.20.2024.09.24.09.43.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Sep 2024 09:43:25 -0700 (PDT) Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.97) (envelope-from ) id 1st8cm-000000016o7-3imQ; Tue, 24 Sep 2024 16:42:52 +0000 Date: Tue, 24 Sep 2024 16:42:52 +0000 (UTC) To: "Jiang, Haochen" cc: "gcc@gcc.gnu.org" , "libc-alpha@sourceware.org" , "binutils@sourceware.org" , "gdb@sourceware.org" Subject: RE: On pull request workflows for the GNU toolchain In-Reply-To: Message-ID: References: MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Joseph Myers via Gdb Reply-To: Joseph Myers Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On Tue, 24 Sep 2024, Jiang, Haochen via Gcc wrote: > I am running regression tests on x86_64 and sending the regressions to > gcc-regression mailing thread, will I need to send to another place or > using another API to do that? I don't expect use of pull requests to change anything about existing regression processing that uses mailing lists. (Systems such as Linaro's that identify a specific commit responsible for a regression might wish to update the PR accordingly using whatever API is available for posting comments on PRs.) Note the recent discussion of making contrib/test_summary able to submit test results to bunsen. Where projects have existing pre-commit CI that puts CI results in patchwork based on patches processed there, I hope such CI would be updated to work with pull requests and update the pull requests with such CI results. > > Beyond putting everything through PRs, eventually I'd hope to have > > merges to mainline normally all go through a CI system that makes sure > > there are no regressions for at least one configuration before merging > > changes. > > > > CI might take long time if not just building but running regression tests > from my current experience, it might cause some inconvenience for > someone who only edits something like MAINTAINER lists. MAINTAINERS list updates are not urgent, it should be fine for them to wait for a batch of approved PRs to pass CI. (The commit rate in GCC is sufficient, and testing sufficiently slow, that I expect a CI system managing merges would need to test potential commits to mainline as a batch rather than testing every individual commit before it goes in mainline.) > Another question is should we also open a PR for backport commits? I've left that question open. I'd hope mainline would eventually move to everything going via PRs; other development branches people might freely continue to commit directly to, though with the option of using PRs to such a branch if the branch maintainers find it useful; and for release branches we'd need to consider the best process separately. > Also for the current commit for obvious, will that policy change? I wouldn't expect such a policy to change. With a system of everything going through PRs, that would mean anyone with write access could approve and merge their own PRs that meet the obvious rule. -- Joseph S. Myers josmyers@redhat.com