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.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 E25661F8C6 for ; Wed, 15 Sep 2021 21:34:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:Content-Type:MIME-Version: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:In-Reply-To:References; bh=Akf2H6u9vL0ZWmlTd0Ralg8JxxVLwAUgHnGj+PoJLcM=; b=O8jdH6OFXCSxuG/6NbLBIMQ83h K8XF3fjVRFnURCDPHts9bZWkrMJDbMwbE8ZMPp4m/zB4pnbQ16S+vzHzDNaJbsXfz3U+pIRw3j8mO suf/uhRX0NF2zl5C4Ys2MsJmTqbzt2Bx2SKCFVmHcr4ehnweOTyvu+9rkwX/bZpUPJI4zRYzNd845 LIe3TKc+ucc/FmrRTevZRpzeZgB5Mj+2wSG3J+96EL8eOOnfdn72VtNemEVTx9vOgsqOXB0C4SJfk CkbJdEUJErHxu7W/YHVMFZ+wVAPcBLgfvlv/Ey2XbuG6+ccPqdYPv4DEoIFIblV+u6B8Q7Tr6pVqf c+zBmBGQ==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1mQcYC-009xlu-7r; Wed, 15 Sep 2021 21:34:40 +0000 Date: Wed, 15 Sep 2021 14:34:40 -0700 From: Luis Chamberlain To: meta@public-inbox.org Cc: Luis Chamberlain Subject: make menuconfig interface for lei / grok-pull Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: Luis Chamberlain List-Id: Greetings, I unsubscribed to most mailing lists thanks to public-inbox. Thanks to public-inbox my inbox went on quite a bit of diet. Now, the way I work though is... I like to hop onto different systems every now and then, and not rely on one central place for everything. This is because when I've done that before I get outages / network outages / etc. So I often have to start from scratch. My use case is I'm subscribed to a few kernel mailign lists and I use mutt with Maildir. I had configured recently pi-piper and grokmirror so that I get only the last 1 year of email from a few set of mailing lists. For this I needed to know the commit IDs for those emails on the public-inbox git mirror for each mailing list. To start from scratch I could go into my logs and figure out what that was again, and start from scratch... but I'm inpsired to just provide a 'make menuconfig' interface for this so that all I have to do is select the mailing list I want to git clone and then dump into Maildir the last 1 year of content for each. Since this time frame of 1 year can be variable, it would seem a good candidate would be to use kconfig to allow those interested to associate the content year by year to git tree and respective commit IDs on each mailing list epoch/git tree. I was hinted using lei would be better though. But I'm stuck: lei init # The next two don't work lei import import https://lore.kernel.org/linux-fsdevel/git/0.git lei add-external git://lore.kernel.org/linux-fsdevel/git/0.git I can use nttp but jeesh, really? Anyway, once the above works, if one didn't want to have the git entire git tree around I gather that I can use something like lei index Then in so far as the date idea I mentioned, I take it the way to go there might be after this to use something like: lei q --only=linux-fsdevel but its not clear if a date is supported as a search term. Also how about doing updates? Is my intended use case better with grok-pull or is there hopes I can end up using lei for all what I have intentions for? My vision is, kernel deveoper would 'make menuconfig' and select a few mailing lists they want to import, then when one is selected new options appear so you can pick the starting year from where you want the import to occur for. Then for each mailing list there is also a refresh thing, so that we can grok-pull differently for each mailing list, which will be handled by systemd timers and a service for each. The reason for differnt times for refresh is updating linux-kernel is not a priority to me, but linux-fsdevel and linux-block are, so I want linux-fsdevel and linux-block to refresh once every 10 minutes, while linux-kernel can update... I don't know once every 8 hours. Anyway, this should all be configurable. And my hope is that developers would not have to know what's going on behind the scenes. All they need to know is that their ~Mail/linux/ directory will eventually be stuffed with Maildir directories for the mailing lists they enabled and they'll be updated as often as specified in their configuration. Luis