From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 8A6F738708CE for ; Tue, 7 May 2024 16:17:30 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8A6F738708CE Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8A6F738708CE Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1715098652; cv=none; b=YvzLwT9A4l4CJPU0gzZk2xIWk209MjPmJHLjuSZoLEOnDcoFmRbT0v9DPsZ8thJ364smOOms5sHpp2TP5yHB/BYLFfw4tj8U+nXko9qohvQb3PXoC2OUNzV7QEie74AreTmBLadoCsqZW42WlDXw9QNmv9pcThMawQkAIswxyLM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1715098652; c=relaxed/simple; bh=9/GFdbndgPRrqngLX72XH6qf0nMvxK3wCyfGgXjVY4I=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=NKMKqvjGSzss6npTwqxlT09jmATDBaYZbnvLW6w0lK4rxds9q8mFKnmjjVrUv8VJTIPCAWD7uaTlobrZX8um0ZG2GUubXdk+Xyy9fcck6YE/IP6DOBVf4Ad0CIJyVVyvG69uDHr3K7G7dlANdF1/o/kOZa9VeAMcvCpMhYtPQ/A= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1715098650; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ryW0/kQHaBWmbT3bXa3ZvRNJiKz8cLxg0s+gOmsVsRc=; b=dFgkCiu63RwvBIREeYDaYklojFAevFAx3MLbhXiHSElyg5mT4GcdNyP7hR0qEIFKD5rTWg jubq5Xlbvmv4j6CE8mqo/rvutJDsA+HU8PaUgTwlupiXsNbxP4ML/USRvyQWH4Vp30mqYn PHfpTrD0/2NqdOVRC8xPV2cYsxKSC+E= Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-299-34hWodvMPn-xicLgp_SCVQ-1; Tue, 07 May 2024 12:17:28 -0400 X-MC-Unique: 34hWodvMPn-xicLgp_SCVQ-1 Received: by mail-lf1-f71.google.com with SMTP id 2adb3069b0e04-51fee4830ebso2701150e87.0 for ; Tue, 07 May 2024 09:17:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715098647; x=1715703447; 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=ryW0/kQHaBWmbT3bXa3ZvRNJiKz8cLxg0s+gOmsVsRc=; b=LVgmorV562xp2gREFlaQ0HWlac3deEIvwB9VK9GLtQG1yFENiXCPURVH/zU1uqgcEI Y2jifpMDq4idAPFkrktE6d8l/UOTep1pJXT8of7j0S45Q2OQaPKUXvH+n1ghKER3Ri/C iqsEy6MD+kPY3LwdhBJJGEmfrbfvc5kjHL4DN4CVuR/tFn4watEBu9U9EMThj4B0ydth wWXCJ5E84wOv9jXvBi6lvY111QFC2O4iGtwj7gJMBC4KtLPn0nYW2bHj4NawpZhvMsR0 LDMLvt76QoF1mlnBWLV2XNdnvP2pue+/LP3jKcuZFo425epdLr1KJzC/vz5VTifbeZ8A yyDQ== X-Forwarded-Encrypted: i=1; AJvYcCVCWkmx/Obb/QWoS296bQbgLIfKMySy2kTYIhpaKAezIbYmlbkSovMeHoeOYSlDYojsyogvhaHI/+kY9grMCdWXQS2a6daaWQ== X-Gm-Message-State: AOJu0Yxvl6XhzK+4f7diqJsfmCuMnIeWauPZd0rgqD3uxWQ3aU9oXrH8 a+5pBKfOHEDPUsVEVbFF+NyBNds2VcVb/oCTdPrDEAYhK2I3Jcu/sQuiCiwQGiAYs+85kJ+gnJ+ KRJSNRIE6qokIRtvkVvi1vkzT4A1sV0TF//NTAoZvUtOOAm6r9OgT5yc= X-Received: by 2002:a19:431e:0:b0:51b:d636:a75b with SMTP id q30-20020a19431e000000b0051bd636a75bmr8553129lfa.68.1715098647348; Tue, 07 May 2024 09:17:27 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFxfcR0EvHDzRx0piLjyWmfbU7uHxRdP6ZAj16QcIqPDj9Gjka8BfpNjeO2sNTFlOHQCUb/Jw== X-Received: by 2002:a19:431e:0:b0:51b:d636:a75b with SMTP id q30-20020a19431e000000b0051bd636a75bmr8553096lfa.68.1715098646825; Tue, 07 May 2024 09:17:26 -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 s16-20020adfea90000000b0034de587ffebsm13329535wrm.4.2024.05.07.09.17.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 May 2024 09:17:26 -0700 (PDT) Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.95) (envelope-from ) id 1s4NVM-005QEt-W0; Tue, 07 May 2024 16:17:25 +0000 Date: Tue, 7 May 2024 16:17:24 +0000 (UTC) From: Joseph Myers To: Fangrui Song cc: Pedro Alves , Simon Marchi , Overseers mailing list , Mark Wielaard , Tom Tromey , Jeff Law , Jonathan Wakely , libc-alpha@sourceware.org, Jason Merrill , gcc@gcc.gnu.org, gdb@sourceware.org, binutils@sourceware.org Subject: Re: Updated Sourceware infrastructure plans In-Reply-To: Message-ID: <1f5a8fc1-6c8-a02f-9787-8bf375a363d@redhat.com> References: <20240417232725.GC25080@gnu.wildebeest.org> <20240418173726.GD9069@redhat.com> <87v849qudy.fsf@tromey.com> <87wmooep76.fsf@tromey.com> <0347e05a-94c6-4ecc-aa8f-cc90358a813d@gmail.com> <20240501202008.GA6469@gnu.wildebeest.org> <874jbh45l8.fsf@tromey.com> <64d0e314-f4e9-4c63-90dd-67a05749e12e@simark.ca> <9a7111c2-d570-4d26-8fe9-f34834ae1eab@palves.net> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, 2 May 2024, Fangrui Song wrote: > > On the other hand, GitHub structures the concept of pull requests > > around branches and enforces a branch-centric workflow. A pull request > > centers on the difference (commits) between the base branch and the > > feature branch. GitHub does not employ a stable identifier for commit > > tracking. If commits are rebased, reordered, or combined, GitHub can > > easily become confused. I'd say we have two kinds of patch submission (= two kinds of pull request in a pull request workflow) to consider in the toolchain, and it's important that a PR-based system supports both of them well (and supports a submission changing from one kind to the other, and preferably dependencies between multiple PRs where appropriate). * Simple submissions that are intended to end up as a single commit on the mainline (squash merge). The overall set of changes to be applied to the mainline is subject to review, and the commit message also is subject to review (review of commit messages isn't always something that PR-based systems seem to handle that well). But for the most part there isn't a need to rebase these - fixes as a result of review can go as subsequent commits on the source branch (making it easy to review either the individual fixes, or the whole updated set of changes), and merging from upstream into that branch is also OK. (If there *is* a rebase, the PR-based system should still preserve the history of and comments on previous versions, avoid GCing them and avoid getting confused.) * Complicated submissions of patch series, that are intended to end up as a sequence of commits on the mainline (non-squash merge preserving the sequence of commits). In this case, fixes (or updating from upstream) *do* involve rebases to show what the full new sequence of commits should be (and all individual commits and their commit messages should be subject to review, not just the overall set of changes to be applied). Again, rebases need handling by the system in a history-preserving way. GitHub (as an example - obviously not appropriate itself for the toolchain) does much better on simple submissions (either with squash merges, or with merges showing the full history if you don't care about a clean bisectable history), apart from review of commit messages, than it does on complicated submissions or dependencies between PRs (I think systems sometimes used for PR dependencies on GitHub may actually be third-party add-ons). Pull request systems have obvious advantages over mailing lists for tracking open submissions - but it's still very easy for an active project to end up with thousands of open PRs, among which it's very hard to find anything. -- Joseph S. Myers josmyers@redhat.com