From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.5 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 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 C31E21F55F for ; Fri, 15 Sep 2023 21:08:42 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=EpKqcgmp; dkim-atps=neutral Received: by mail-vs1-xe2a.google.com with SMTP id ada2fe7eead31-450b8d61550so967858137.0 for ; Fri, 15 Sep 2023 14:08:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1694812121; x=1695416921; darn=public-inbox.org; h=content-disposition:mime-version:message-id:subject:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=1jOxLbq/XbVhCDZUKSHw0N1oXngnJdAzaPp8hWg/yFA=; b=EpKqcgmpOJ2sHhtMCeGzQZ33xBv2AA0pWM5s5w6A/80FguljVO9vsNz2bjJvkELZGr A2xlnHcIv9KVWauVQxD4elyk/uWSn8ALkFuIOL3s6oO/yoZUFYwfJknvk5lTY7tChOns XTlDr4MVYOpWfUuPOSaRHyCJRg6z34cY3EoG0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694812121; x=1695416921; h=content-disposition:mime-version:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1jOxLbq/XbVhCDZUKSHw0N1oXngnJdAzaPp8hWg/yFA=; b=aHC00QSqfF64CWOfG6Q3paMFQg6KuiYV9MVsgntm4msFVkYbK3vHQsgfWhYnexERRr kYjrKF8hhbf7z/0gmPblSMvxlRVOI2PGYptG+cPWJz6oTU7bZtXehrUxFKhrTKZP2H1l RTTejqcu0MK0oDIplbyXzOooKtFycoPjvVb4y/c0cnKhNrQsLDhwRe01VzCYEs0zX5Qp pVteKMLfAUrjeLw1prbtU3RvM0bMEM+C35b/vIwhQ+sQFycakb3du3cPqVgXd6VUTIAe ICL7sgyWL5MM6mDAWNdFNPGVnYvt7IMyfx9DuxOw2oMkBJGUoQtQdZyckWY4Z/bE/D6y yqyg== X-Gm-Message-State: AOJu0Yy/WRevQ+SmNyQZexBqQP7yHG1Si4Ofuze6NOHsLKK0dvfyi7GF kU+Y8N30Z43N9l7H8e7Gxj2jNPblhT/1uOS2WeU= X-Google-Smtp-Source: AGHT+IFddmBXVrQp7cnKZhzKfEgtSdcJAdq54Gq/cOgpj02rBepbJqVAUJq9m2rfav0JPuQD4nGzCg== X-Received: by 2002:a67:cf47:0:b0:450:a7ff:55ab with SMTP id f7-20020a67cf47000000b00450a7ff55abmr2916903vsm.21.1694812120837; Fri, 15 Sep 2023 14:08:40 -0700 (PDT) Received: from meerkat.local ([209.226.106.110]) by smtp.gmail.com with ESMTPSA id r14-20020a0ce28e000000b0064f50e2c551sm1551231qvl.1.2023.09.15.14.08.40 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Sep 2023 14:08:40 -0700 (PDT) Date: Fri, 15 Sep 2023 17:08:32 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: RFC: lei searches managed by users in git Message-ID: <20230915-conjure-exuberant-d527e8@meerkat> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: I am curious what is the best approach to have a centrally managed set of lei searches, for example via config files tracked in git. For example, the file could look like this: mricon.toml: [search.torvalds] # All mail sent by torvalds q = 'f:torvalds@linux-foundation.org' [search.floppy] # Any messages talking about floppies or touching floppy code q = 'dfhh:floppy_* OR dfn:drivers/block/floppy.c OR s:floppy OR ((nq:bug OR nq:regression) AND nq:floppy)' I could then have a small wrapper maintaining saved searches and making the mailboxes available via special newsgroups like: org.kernel.lei.mricon.torvalds org.kernel.lei.mricon.floppy The goal is to make it possible for maintainers to define their own set of saved searches and have access to them at kernel.org via imap/pop3/nntp. It's easy to write a simple wrapper that would invoke lei-edit-search and replace the search string when there are updates to the config files, but I'm curious if you already have thoughts on how to best implement something like this. My biggest concern is someone committing an invalid query and not receiving any more email as a result -- so having a sane way to validate the query before sticking it into the saved search would be handy. -K