From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 500FC3858413 for ; Thu, 18 Aug 2022 14:40:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 500FC3858413 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 27IEe1FC021637 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Aug 2022 10:40:05 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 27IEe1FC021637 Received: from [172.16.0.95] (192-222-180-24.qc.cable.ebox.net [192.222.180.24]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id CFDBB1E21F; Thu, 18 Aug 2022 10:40:00 -0400 (EDT) Message-ID: <3ed574a5-e539-158e-2102-0d6aa4ec4ae8@polymtl.ca> Date: Thu, 18 Aug 2022 10:40:00 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: inbox.sourceware.org experiment Content-Language: fr To: Mark Wielaard , "Frank Ch. Eigler" Cc: Overseers mailing list References: <20220813141403.GL5520@gnu.wildebeest.org> From: Simon Marchi In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Thu, 18 Aug 2022 14:40:01 +0000 X-Spam-Status: No, score=-3032.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2022 14:40:33 -0000 On 8/18/22 09:50, Mark Wielaard wrote: > I am not sure that is my main interest in public-inbox, but yes, I do > really like public-inbox because it allows tools like b4 (which I have > already tested against our instance) and piem (not tested yet) to > easily pick up and apply patch emails. > https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/README.rst > https://docs.kyleam.com/piem/ > > I think others will also use those (or similar) tools. But I primarily > expect users to use the public-inbox archives as a way to access the > mailinglists without having to subscribe, but still be able to easily > get the actual (raw) messages (either through git, atom, mbox, nntp or > imap) to follow the conversations. Which I think is the main > interesting thing public-inbox offers. For me it's: - Being able to download the raw emails in order to apply patches or to properly reply to messages on lists I'm not subscribed to - I never thought about the feature Mark mentioned, about download an mbox for a given query. But if you want to download a very long patch series to apply it locally, it could be useful. - Better display and browsing to read longer threads that span multiple months. For example, trying to follow this thread on Mailman would be complicated: https://inbox.sourceware.org/gdb-patches/20220428033542.1636284-1-simon.marchi@polymtl.ca/T/#r5f31e373eeb958095add41686e0ae7d1dcac9f1a - Search: I find it useful to be able to find a message by Message-ID. For instance, I'm reading the message in my client, and I want to send someone the link to that message in the web interface. In my instance (pi.simark.ca) I can paste the Message-ID in the search box and it gets me directly to the right message. On inbox.sourceware.org, I don't see the same search box, maybe it is because of the V1/V2 thing you have been talking about? - Not super important, but I like that the URLs to messages contain the Message-IDs. This way, in a distant future where inbox.sourceware.org does not exist anymore, someone with the archive can still find out which message a given URL refers to. A bit like if I give you this URL: https://gitlab.com/gnutools/binutils-gdb/-/commit/243cf0f69c36c4ee09c3c2b0bc7a97dc16119c51 and Gitlab does not exist anymore, you can still find you which commit I am talking about if you have a copy of the binutils-gdb git repo. Also, you were talking about space. If you want to save some space, I don't think it's very useful to have the *-cvs lists on there. And there are lists that are pretty much dead that you could skip too. Simon