From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,URIBL_RED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 327831F5AE for ; Mon, 26 Apr 2021 18:20:24 +0000 (UTC) Received: by mail-qk1-x735.google.com with SMTP id y136so25372491qkb.1 for ; Mon, 26 Apr 2021 11:20:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=IlK0Li+1Cyk4mvwGTXdEC74uv9GsjUP+hnio+4/FnwQ=; b=Bhdlu3AmT1RVV++D27sTg8M8Ob9NyVySIsIJAVPrbhlvL5MXC8Vg/esEUpvMNED7x2 P5e5cltF6xVsOtkUw3jqJeK8tX1aSYUoKU/9GbVbrID8uzrHP2ZDvicRyszI1C/8rO6r O+iC0r1FBYkd7atcs1kbF99X7qQjgN7GApQT8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=IlK0Li+1Cyk4mvwGTXdEC74uv9GsjUP+hnio+4/FnwQ=; b=BPY2YMOgHAw0I2W8sVviFYBeMBGu27pSQDzx6ImtmFVIY02XlKBY0vhbwl9nXkqY1R A+vtKKO6z6AQGFwaEfGPy9nNNVjvgX2FQI9hB9xl04vgVleyno+55fHdXr60PIRnmehr 6VBlDXDhotB6ZIDouAky1elVYcTCzw9yxALKZ92o5flj1PHzHJ6bW5P+5UPirt2rG2/O l7Bfqt++vkSfzVyRE4m0Hhz/3UVJD/r77acS7Cc3Q8k3VkQGQ+E1AyDjb8Pg929bolAp G+12Ix6dOrO5A5T71RM3AC6D5jYlIj7/0oqRr5KtBDjy9VG5pRHxbQjmE18hy4u9mulY prJQ== X-Gm-Message-State: AOAM530SkmwlxfPPaCXZBGIgeH4eBXouopYmCecZcQywvcdmlFykeU7T VjdeQB9xQ2yB3Pq1s9Ox0dD1IQ== X-Google-Smtp-Source: ABdhPJwPUDeHK7hpzOuVg1NPA+36Cv72wF73zuj7Sv4HUEFcTU2wYNVNagNkWxmpAGT4gNTei6Ltcw== X-Received: by 2002:a37:a053:: with SMTP id j80mr7161421qke.443.1619461222760; Mon, 26 Apr 2021 11:20:22 -0700 (PDT) Received: from nitro.local (bras-base-mtrlpq5031w-grc-32-216-209-220-18.dsl.bell.ca. [216.209.220.18]) by smtp.gmail.com with ESMTPSA id a10sm12133474qtm.16.2021.04.26.11.20.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Apr 2021 11:20:22 -0700 (PDT) Date: Mon, 26 Apr 2021 14:20:20 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: lei-managed pseudo mailing lists Message-ID: <20210426182020.olonbxkc6a2gfzl3@nitro.local> Mail-Followup-To: Eric Wong , meta@public-inbox.org References: <20210426164454.5zd5kgugfhfwfkpo@nitro.local> <20210426173726.GA22986@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210426173726.GA22986@dcvr> List-Id: On Mon, Apr 26, 2021 at 05:37:26PM +0000, Eric Wong wrote: > > The latter is specifically something I think would be of interest to kernel > > folks, so I envision that we'd have something like the following: > > > > - a maintainer publishes a configuration file we can pass to lei > > The command-line might be enough, the pathname of the current > state/config file is a bit tricky and tied to its output. > I suppose "lei import-search" can be a command, though... Excellent, excellent. How well does it deal with the situation when the search parameters change? > > - our backend lei process uses all of lore.kernel.org sources to create and > > continuously update a new public-inbox repository with matching search > > results > > There's already some accomodations for that in LeiSavedSearch > which can present itself as a PublicInbox::Inbox-ish object to > PublicInbox::WWW (untested). > > Searching an within LSS isn't implemented, yet, but I think it's > doable w/o extra Xapian storage. > > However, git object storage isn't duplicated, which is nice for > local use (instaweb-like), but supporting clone/fetch isn't as > natural... I'm thinking we need the ability to make it a real clonable repository -- perhaps without its own xapian index? Actual git repositories aren't large, especially if they are only used for direct git operations. Disk space is cheap, it's the IO that's expensive. :) If these are real clonable repositories, then it would be easy for people to set up replication for just the curated content people want. > Perhaps supporting a v2 inbox as an lei q output destination > is in order: > > lei q --output v2publicinbox:/path/to/v2 --shared SEARCH_TERMS > > --shared would be "git clone --shared", the new v2 inbox can > use ~/.cache/lei/all_locals_ever.git/ as an alternate and not > duplicate space for blobs. Not really worried about deduping blobs, but I'm wondering how to make it work well when search parameters change (see above). E.g.: 1. we create the repo with one set of parameters 2. maintainer then broadens it up to include something else 3. maintainer then decides that it's now *way* too much and narrows it down again We don't really want step 2 to lead to a permanent ballooning of the repository, so perhaps all query changes should force-append a dt: with the open-ended datetime of the change? Or do you already have a way to deal with this situation? > > - we set up a mlmmj list that doesn't receive any direct mail but is only fed > > from saved search results; people can subscribe/unsubscribe as they would > > with any other mlmmj list > > > > Any particular reason this wouldn't work? > > Nope :) As long as all the data formats can interoperate > (mostly RFC5322/2822). "lei convert" is nice, too :) Great! I believe this will help untangle the current situation with "where should I send this kernel patch". I want "just send it to linux-kernel@vger.kernel.org" to be a valid option again. Participating subsystems can then define what patches they want to see by setting up pseudo-lists and letting participating reviewers/maintainers subscribe to them via their preferred mail delivery mechanism. -K