From: Stavros Ntentos <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, firstname.lastname@example.org Subject: Re: [PATCH v1] git-send-email-reply: Append subject Date: Sat, 27 Mar 2021 10:39:46 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <20210326213517.GA5730@dcvr> > 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.
next prev parent reply other threads:[~2021-03-27 8:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-26 16:31 Stavros Ntentos 2021-03-26 19:36 ` Eric Wong [not found] ` <CAHMHMxVS4tVvUYvWUmk8L8oqPPxtYW-MF_57Vwuzug-asWQiQg@mail.gmail.com> 2021-03-26 21:35 ` Eric Wong 2021-03-27 8:39 ` Stavros Ntentos [this message] 2021-03-27 9:54 ` Eric Wong 2021-03-27 14:01 ` Σταύρος Ντέντος 2021-03-27 19:32 ` Eric Wong 2021-03-28 16:00 ` Σταύρος Ντέντος 2021-03-28 22:58 ` Eric Wong
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v1] git-send-email-reply: Append subject' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/public-inbox.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).