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.4 required=3.0 tests=AWL,BAYES_00,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-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id AE1EC1F46C for ; Tue, 21 Jan 2020 22:29:27 +0000 (UTC) Received: by mail-qt1-x842.google.com with SMTP id e5so4081022qtm.6 for ; Tue, 21 Jan 2020 14:29:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition; bh=GNeS6mooF3Q354GYxLb0hpS19PJ+RvOMNeIMmjXqlcI=; b=RgNC4Jwv2Wl+uhbQ1OZd9HJO0ximwP/2dqKlhDkW5B8xmOnyxt6MDvfV4SQUnwgZR5 Q+VTxXcDpl2pfBDHLTXHvk4/bGxuDN9UbGUisogsSWVTq7Amkk9ph927n4o/Vu8fUzS9 0xwALRSiJW/NPSX5eBz5pCUBMQfAgUByTmYzE= 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:mail-followup-to :mime-version:content-disposition; bh=GNeS6mooF3Q354GYxLb0hpS19PJ+RvOMNeIMmjXqlcI=; b=B48sIiRbzwE2vdTBrgEX4FGrTFcAXAnAR1JLoHNE2tXrbSXCOdJi+O/ut6MInbgby3 hxVi3nZnEM6ruKWrEjHPxjU2eQLkWBvzCw79Oa85lVoN9zkTyj33YJwT48GKaH1Y+eYm QVagmdFHEOzW80KDZozaCfF2a0rAhQ6W5cMVziEs8nty3gghmuAjnIM5zlka2MtwADM7 MjS3vlgd7YRdQ/EqmYn1bNC2FCkfxcYj2D4C3FSR5tILACnHd1kn6a9SZRXjuqoXgd3P tnoJrUibSYh8bOxa/zQf97xDxRzCgpvhWauOD6RtcEzNdqlOd4ao1SP3Y89GRFVYbhQ+ w4IA== X-Gm-Message-State: APjAAAUmo7IDby2S4vfwATSZlLv+xfXe9onzi7ws1/bH4WKepHFKSzd+ eHzr4NFRmrC82PXgm2X0Uf8VYMopF2x2lH4u X-Google-Smtp-Source: APXvYqzl98WUvieIy5zpUHp/mXEBULPkmdlx0BilkiwK682gHjK7hl5wtq8CGDFMS+iI4dE9n/EwRA== X-Received: by 2002:ac8:1a69:: with SMTP id q38mr6607185qtk.96.1579645766128; Tue, 21 Jan 2020 14:29:26 -0800 (PST) Received: from chatter.i7.local (107-179-243-71.cpe.teksavvy.com. [107.179.243.71]) by smtp.gmail.com with ESMTPSA id m27sm20248480qta.21.2020.01.21.14.29.25 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Jan 2020 14:29:25 -0800 (PST) Date: Tue, 21 Jan 2020 17:29:24 -0500 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Minimalist public-inbox feed: sendmail-pi-feed Message-ID: <20200121222924.ioz5ve2sg65zcuoy@chatter.i7.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hi, all: I was trying to create a "simplest possible" way to maintain a public-inbox developer feed, and this is the end-result: https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/sendmail-pi-feed It's written to be used with git-send-email, but can, theoretically, be used with any tool that accepts custom sendmail command paths (e.g. mutt) -- though if used in that capacity, it needs more features to make sure that private mail is not added to the feed. For example, there can be an "allowlist" of addresses to match against "to" or "cc". At the moment, this is more of a proof of concept and I wanted to share it with you all for early comments. The main goal was to avoid introducing too many dependencies, such as perl and its many cpan modules, while producing valid public-inbox feeds -- so this script is literally 50 lines of bash. :) >From the readme section: ---- Simplest configuration is to set the following in your git config file, either per repository, or globally in ~/.gitconfig if you want a single developer feed for all your work. [sendemail] smtpserver = /path/to/bin/sendmail-pi-feed [sendemail "sendmail-pi-feed"] # the directory where to put the feed (will be created with --init) inboxdir = /path/to/toplevel/public-inbox-dir # if not set, the epoch will be 0, which is strongly suggested; # if you increment it for some reason, make sure you don't skip # numbers epoch = 0 # if defined, will pipe stdin to this command as well, in case # you want to actually send out the patches in addition to writing # them to the public-inbox feed; leave undefined otherwise sendmail = /usr/sbin/sendmail Once this is done, run "sendmail-pi-feed --init" to create the feed. During the init process, you will be asked whether you would like to PGP-sign the commits, which is strongly recommended if you already have PGP-signing set up on your system. After the --init is complete, you can use "git send-email" as you normally would and all patches will be automatically added to the feed. You can then publish the feed on any git hosting service by setting a remote and performing a git push. If you would like to auto-push the feed, you can add an appropriate post-commit hook. ---- Thoughts? -K