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.6 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.2 Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 104A81F8C6 for ; Thu, 2 Sep 2021 21:12:29 +0000 (UTC) Received: by mail-qk1-x72d.google.com with SMTP id t4so3722876qkb.9 for ; Thu, 02 Sep 2021 14:12:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=SViHGDa4FGtsxM81CgDODuFIY0iwh6Zvh738AxsRHGY=; b=E2MbeeTirHlqzOuw0STWLA5jIXfCTZIm+msAWzwn2yVJSzPo+eb/HK+61pSQcpvmVM whGF5d3o7KNagSuLM7hAjOzfsEVWjViTn17sY5/ozqvg45rKBpvEzW4AFvIVKcW36tu8 FB7owSWjiDmek6ffyQPMM1hthi00AsG4WfEfo= 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:subject:message-id:mime-version :content-disposition; bh=SViHGDa4FGtsxM81CgDODuFIY0iwh6Zvh738AxsRHGY=; b=JLG75grLUncjl/c3Dl8NGI7jWE0PU+uNVMGf4DNphw8rh4tf2yZEUTQmw162+r6J8C VANwjnTS0PnQ0Ticfcv8nGC4MFYSFyvHBaL5KmE39ji+lenF9gkUPisTpoOu1o7AXGGz bpgJhj7CpiwT+JMHNq3IMSV5JNkv+7dN/pYqQ3xwQbCkaaDtuEQUKbV3jPGIeUqrHFHe 4GyNrcSyEP6Cafh5DboB0n7OGSJZHolNHPVhz5EflTkB+32BcwyCuoYeXZxaVFWl6XlK gUP/7Lsy6tDTcpHsJEqg/jCEDE/HM7gPLsvju0LtTBmr7Sn9GF3frWdFtOsfiQQTM0Ku Ndrg== X-Gm-Message-State: AOAM5332q0s1eB/CDjTEqrQ0iMqWQilak1pWj8rN1P2xrVmV1AcxhQVE WWDLSRXGbaNMpStYVqxYEoG3T5n9hzdI7tLW X-Google-Smtp-Source: ABdhPJxO2fYiJVohH8JhV2Hfu05qDas+nl/xVq/O/ePdu5N8Yy3kiu4o85+QPPVxCQ1LoxNDh3u62A== X-Received: by 2002:a05:620a:1474:: with SMTP id j20mr89907qkl.305.1630617147465; Thu, 02 Sep 2021 14:12:27 -0700 (PDT) Received: from meerkat.local (bras-base-mtrlpq5031w-grc-32-216-209-220-181.dsl.bell.ca. [216.209.220.181]) by smtp.gmail.com with ESMTPSA id j18sm2316130qkl.12.2021.09.02.14.12.26 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Sep 2021 14:12:26 -0700 (PDT) Date: Thu, 2 Sep 2021 17:12:25 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Showcasing lei at Linux Plumbers Message-ID: <20210902211225.pmnykwcwcxeaunt5@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Eric: I am getting ready for my presentation to the Linux Plumbers (happening in a few weeks, eek), which is based around lore, lei (I see what you did there) and search-based subscriptions. I want to make it hands-on with practical examples, which is what developers would appreciate more than just dry manpages. I am in the process of wrapping my head around lei tooling, but I may have some questions in the process, so I wanted to start this thread as a record of my poking at it. :) What I currently have: - an imap mailbox - lei configured and installed locally (in a debian container) The goal is to illustrate how to use this to start "receiving" mail for a subsystem without subscribing to any of the lists. The example I have in mind is the LANDLOCK subsystem, and the reason I picked it is because it already has a well-defined set of search criteria we can use: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n10462 LANDLOCK SECURITY MODULE ... F: Documentation/security/landlock.rst F: Documentation/userspace-api/landlock.rst F: include/uapi/linux/landlock.h F: samples/landlock/ F: security/landlock/ F: tools/testing/selftests/landlock/ K: landlock K: LANDLOCK This means we want to configure lei to grab any mail from lore.kernel.org/all/ that matches this query: dfn:Documentation/security/landlock.rst OR dfn:Documentation/userspace-api/landlock.rst OR dfn:include/uapi/linux/landlock.h OR dfn:samples/landlock/ OR dfn:security/landlock/ OR dfn:tools/testing/selftests/landlock/ OR dfhh:landlock https://lore.kernel.org/all/?q=dfn%3ADocumentation%2Fsecurity%2Flandlock.rst+OR+dfn%3ADocumentation%2Fuserspace-api%2Flandlock.rst+OR+dfn%3Ainclude%2Fuapi%2Flinux%2Flandlock.h+OR+dfn%3Asamples%2Flandlock%2F+OR+dfn%3Asecurity%2Flandlock%2F+OR+dfn%3Atools%2Ftesting%2Fselftests%2Flandlock%2F+OR+dfhh%3Alandlock I'll want to retrieve any threads and follow-ups and upload them to my imap landlock folder -- and then run in the background and just continuously update things as more mail comes in, so I don't have to remember to run anything manually. What succession of lei commands would accomplish this? Thanks for your continued help. -K