From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id Ga2LH2BTNGZC2gMAWB0awg (envelope-from ) for ; Thu, 02 May 2024 23:00:48 -0400 Received: by simark.ca (Postfix, from userid 112) id 6E5831E0CE; Thu, 2 May 2024 23:00:48 -0400 (EDT) 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 547D71E030 for ; Thu, 2 May 2024 23:00:46 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id BAEB2384AB58 for ; Fri, 3 May 2024 03:00:45 +0000 (GMT) Received: from sam.airs.com (sam.airs.com [64.13.145.90]) by sourceware.org (Postfix) with ESMTPS id 979D7384AB58 for ; Fri, 3 May 2024 03:00:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 979D7384AB58 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=airs.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=airs.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 979D7384AB58 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=64.13.145.90 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714705208; cv=none; b=XMe5YrpOmZcj+fKsIqqR4uZfEgXiVYTsR7H9aoHHuEgge+YBqAtYPskey4Pka7mKC2OTWq8yYjb36QEgWCgYHve2vLdVslUIULIli4SFKo2x5p1JTsH6kgptux1hB31UaiDuzn4e7CUffymqPOe3cTVnlI5n4NCymTbQVVTxPEA= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714705208; c=relaxed/simple; bh=unofc4g9NmPSHFxpw81U8Frvc2SdmMLlPCEtRZxRvmo=; h=From:To:Subject:Date:Message-ID:MIME-Version; b=oxryMQ9naUEPCoXev0sMgCgEcYExe0lMlqML74wZSJTVXxPVZsSfRgrHEke0XIm3QaIHu0u7JsL6wC+YLlPB7164LV+wCO1ELiLneB/KjeyYQB9I5WC5VCOFvXcTsM1c5uX9t7hKV2qcremk9qagjXbFJqfvqgFxTAe5YEbcses= ARC-Authentication-Results: i=1; server2.sourceware.org Received: (qmail 38883 invoked by uid 10); 3 May 2024 03:00:03 -0000 Received: (qmail 1375126 invoked by uid 1001); 3 May 2024 02:59:32 -0000 Mail-Followup-To: mark@klomp.org, jason@redhat.com, pedro@palves.net, jeffreyalaw@gmail.com, josmyers@redhat.com, libc-alpha@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org, sergiodj@sergiodj.net, binutils@sourceware.org, tom@tromey.com, overseers@sourceware.org From: Ian Lance Taylor To: Pedro Alves via Overseers Cc: Mark Wielaard , Jason Merrill , Pedro Alves , Jeff Law , Joseph Myers , libc-alpha@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org, Sergio Durigan Junior , binutils@sourceware.org, Tom Tromey Subject: Re: Updated Sourceware infrastructure plans 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> <0d0af1d9-21f8-4c60-ad4c-cd82c0c0cabb@redhat.com> <20240501212618.GB6469@gnu.wildebeest.org> Date: Thu, 02 May 2024 19:59:32 -0700 In-Reply-To: (Pedro Alves via Overseers's message of "Thu, 2 May 2024 16:33:30 +0100") Message-ID: <86h6ffob1n.fsf@pew.airs.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org 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: , Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Pedro Alves via Overseers writes: > When GDB upstream tried to use gerrit, I found it basically impossible to > follow development, given the volume... The great thing with email is the > threading of discussions. A discussion can fork into its own subthread, and any > sane email client will display the discussion tree. Email archives also let > you follow the discussion subthreads. That is great for archaeology too. > With Gerrit that was basically lost, everything is super flat. And > then following > development via the gerrit instance website alone is just basically > impossible too. > I mean, gerrit is great to track your own patches, and for the actual review > and diffing between versions. But for a maintainer who wants to stay > on top of a > project, then it's severely lacking, IME and IMO. My experience is the exact opposite. As I'm sure you know, Gerritt supports specific comments on a code review, and discussions on those comments are tracked separately. For a complex patch, or series of patches, you don't get lost in lots of separate discussions, as Gerritt tracks them all for you separately. But it's true that to use that effectively you have to look at the web interface. The comments are available via git commands, but not in a directly usable format. Ian