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.7 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 C438D1F8C7 for ; Fri, 3 Sep 2021 15:15:03 +0000 (UTC) Received: by mail-qk1-x734.google.com with SMTP id f22so6095248qkm.5 for ; Fri, 03 Sep 2021 08:15:03 -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:references:mime-version :content-disposition:in-reply-to; bh=cAfXNa7spRTUq2485HAie0Og9kEw+oUPNV5FrBM9jyQ=; b=ZJMUGCRdwyxSnzhRfyuQL8M2UK90MK3s5QnhLJLalfNE24goE4Vas7F4satWp4kuvK P0EQ5ZFqFLA4HpYa5vuW4t1XRJlK1gsXERhSjRPorggZna5f9rDZX3hNc8qv5gYD3FSW zM9noEcoKg/KK17m7acLTFfcPc8eAPm6gtB7M= 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:references :mime-version:content-disposition:in-reply-to; bh=cAfXNa7spRTUq2485HAie0Og9kEw+oUPNV5FrBM9jyQ=; b=OW8HLndfFK7ZbWAjOGvuWIld+KKuD0segkKYuuVBQibkEyl7YGrKWYFeiMrsqD2sh8 EofpViOMRBcvplG4Nn5102V1tu4WfURk7TJalDq52DqM2JxqiSiI3rq1aeTixVuIXe1E mrDhYTRrWN+oFURNg+T+wkysrHn+LNKQxBRIOnpvRtcErwa3ZoI72x6TIm/SAH+aegY2 /5N+IW9GYnFQP4jieoMNewcxIUVJ+UsfY8EfafG292Hmqsjfut1YVq9i80tQg0jzBt0o bghhxwNgIoByBb1hHCThi13IK2ArfPohLG9n3gBmkbZWuHDNUwsUb6+dUZnsXnE3cy+E Ms8Q== X-Gm-Message-State: AOAM531NOKw7OSX+hYYOxI1GGmuwLdLLJAAaFnO61jopK3HK5RlmqHL4 ZsYwGfUPoVvAu/zq5ZlJLJxgJSE1MPA38hBY X-Google-Smtp-Source: ABdhPJyZb/TsiixWJTYDRA3upzuTZro6cNq5vrxTFkvMusoP6YBUoVsREGBgcIRiGMLUetwO8uyZ7g== X-Received: by 2002:a05:620a:79b:: with SMTP id 27mr3868914qka.248.1630682102531; Fri, 03 Sep 2021 08:15:02 -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 w18sm3187927qto.91.2021.09.03.08.15.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 03 Sep 2021 08:15:02 -0700 (PDT) Date: Fri, 3 Sep 2021 11:15:00 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Showcasing lei at Linux Plumbers Message-ID: <20210903151500.h72mzcpqixgtytjs@meerkat.local> References: <20210902211225.pmnykwcwcxeaunt5@meerkat.local> <20210902215850.GA5063@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210902215850.GA5063@dcvr> List-Id: On Thu, Sep 02, 2021 at 09:58:50PM +0000, Eric Wong wrote: > Fwiw, most of the functionality works much better with Maildir > because of potential password prompts needed for IMAP and > interactivity required. Okay, I'll try this out with maildir for now -- it's easy to hook mbsync into the process if desired. > OK, there's two main commands, "lei q" and "lei up". > Both of which may prompt for passwords depending on how > git-credential is set up: > > # the destination, could be Maildir > MFOLDER=imaps://user@example.com/INBOX.landlock > > # initial search: > lei q -o $MFOLDER -t -I https://lore.kernel.org/all/ --stdin < ( > 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 > ) AND rt:2.months.ago.. > EOF > > # update whenever, may prompt for IMAP password, but could be > # cron-ed or similar if passwords are cached > lei up $MFOLDER > > # Optional: tweaking the search parameters can be done via > lei edit-search $MFOLDER Yep, that seems to work fine. Question -- I noticed that lei just issues a regular query, retrieves results with curl and then parses the output. Is there a danger of potentially running into issues with parsing the regular HTML output if it changes in the future? -K