Re: [PATCH v1] git-send-email-reply: Append subject

[Stavros Ntentos <stdedos@gmail.com>]

> 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.