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-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 3470F1F9FD for ; Sat, 27 Mar 2021 08:39:53 +0000 (UTC) Received: by mail-wm1-x332.google.com with SMTP id u5-20020a7bcb050000b029010e9316b9d5so4150808wmj.2 for ; Sat, 27 Mar 2021 01:39:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=ynfDdF/ZB3jBo0XiyAb0UxEz9nT9Uj1S8oqJW2XbWeQ=; b=q+m8ZUm8QGZeVdj+edZK/BZLodeIkTNlbWkmrrmwqi6LufIciK4UDPcstDwduzPUWv PiUl3vSLWw4817FkTLvvWmuvGNp2q7clQ+UleYqSGbFK2bAINPjyKBKP38CWQUS55SaY kcUACBGKwLjsVcSQTndxkP+0YgmTQJ+1/WnY2FLN62gQBRvy6AcnosQ97M6Ou2rzEMML L6BVf37BHAM7IqmUvSqqPjzLQ0c1J7uWcWB/PR+Bklhzn1iPObuRSkV8eLdSIHsfQ5kG OfG0b48FyAh09Sx7p5E02aRMK6zGeA80OCEcox7Gm5wVg24fk96hYtmiEMhNraKQzCvz aWTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ynfDdF/ZB3jBo0XiyAb0UxEz9nT9Uj1S8oqJW2XbWeQ=; b=S7C+0sfamhFsS1i6LwCvpGWU4AsqzE0REoD8f+/KZCJMboMOojIDPIIKO091/Fxn+j ZoNjrDEK3Ph6rARefq++GZg1g8eexf+8azGrAqFNt/EMJTvnr8COg5l88dIwJmAr7Jer Pma+8/CNH75aKSH0ZWcdJBStwDGY8tNBhlVTPw6U/JFzAdTTNAOcaVSF5dtC8xG86nSw OXbHujKVocz0HUpY7tseXX7iV40dxlzjvl45oDmfCVN6oF2FKEK/1LHLXdKAV1RpHrJn fCu1Ecj0inDMBsu1VSOrAnVQKU6gunO1yG87/Zge64lbdYPRuMnqfoxHdSraAwxZwuBH nh9A== X-Gm-Message-State: AOAM531N+mNkpgJcckMuu2/Nr1xlkxh2KEI9E4HL3yjm0alozk4MlKvR 8yll45Xg1zniXcF0kL4Q7bg= X-Google-Smtp-Source: ABdhPJy3MkpXPOw59c5Ammox8QNBms3oHyynKNN67YHn2S7vV2BIGDi0Jgh9gezjIg/tyyib1dWOGA== X-Received: by 2002:a1c:f20d:: with SMTP id s13mr8660943wmc.92.1616834389999; Sat, 27 Mar 2021 01:39:49 -0700 (PDT) Received: from localhost.localdomain ([2a02:85f:2a0a:9300:501f:ca6d:3b18:1e72]) by smtp.googlemail.com with ESMTPSA id z66sm15765214wmc.4.2021.03.27.01.39.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 27 Mar 2021 01:39:49 -0700 (PDT) From: Stavros Ntentos X-Google-Original-From: Stavros Ntentos <133706+stdedos@users.noreply.github.com> To: e@80x24.org Cc: meta@public-inbox.org, stdedos@gmail.com Subject: Re: [PATCH v1] git-send-email-reply: Append subject Date: Sat, 27 Mar 2021 10:39:46 +0200 Message-Id: <20210327083946.30726-1-133706+stdedos@users.noreply.github.com> X-Mailer: git-send-email 2.31.0 In-Reply-To: <20210326213517.GA5730@dcvr> References: <20210326213517.GA5730@dcvr> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: > Fair enough, pushed as 90ca1ac28edb2e8a64c30bb4be723643c646df89 with > t/reply.t adjustments: > > https://public-inbox.org/meta/90ca1ac28edb2e8a64c30bb4be723643c646df89/s/ Cool! ... but, I don't see it e.g. here :-p https://public-inbox.org/meta/20210326213517.GA5730@dcvr/ I thought you said you deployed it :/ > Yes, already deployed to the server that runs public-inbox.org/meta > (I do development on that server :x) Would it make sense for you to "symlink" /meta/ to /public-inbox/? (as it is for git.git --> /git/) > Also, please don't send HTML email. It wastes storage, bandwidth, > and CPU cycles (spam filtering) for everybody involved. It was definitely not my intention to mess up systems. It was one of the last things I did that night (my timezone), and I thought: just a "LGTM" response is maybe not that nice, and I am a bit too tired to full-fletched git-send-email reply to it. (because so far, I am manually copy-paste-format-reply from my text editor). If anyone has more instructions on how to meld Gmail with git-send-email and friends, for an inbox that doesn't normally reside in a said computer, I am all ears. :-D > I try to stick to widely-packaged dependencies to avoid the need > for things like Docker (which I've never used). It should be > reasonably easy-to-install on most GNU/Linux and *BSD distros; > do you use anything exotic that's not covered in INSTALL and > HACKING? It's not about using something "more fancy"; it's just about keeping a "separatation" between my normal system, and the system I want to develop x-or-y project. Docker allows me to deploy any OS (debian stretch) above any OS (in this case Ubuntu bionic) in its pristine state, super light-weight and ready to go. tl;dr: With some (maybe not so much) considerable work from your side, I could be looking at a minified public inbox clone, with some lightweight repo and e-mails inserted, to which I could've made my changes, and (in that terminal) type `make deploy`. Then, I would've seen here https://localhost/meta/20210326213517.GA5730@dcvr/ (or some other equivalent page) what I expected to have seen here https://public-inbox.org/meta/20210326213517.GA5730@dcvr/ Then, when I was done, I would've written `docker rm -f $container_sha`, and poof! Nothing ever existed, nothing is running, no resources used (except caches of the "docker layers" used to build the docker image) Across any docker-supported system, no matter what your base is. (Okay, maybe it wasn't so much tl;dr after all :-D) It's not so hard to insert it (albeit clumsily) into your toolchain. You can even write it quite easily, or I could even convert you a "deploy all".sh script you may have laying around on top of debian buster.