From: Eric Wong <e@80x24.org>
To: "Σταύρος Ντέντος" <stdedos@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH v1] git-send-email-reply: Append subject
Date: Sun, 28 Mar 2021 22:58:36 +0000 [thread overview]
Message-ID: <20210328225836.GA17258@dcvr> (raw)
In-Reply-To: <CAHMHMxUFhut=ER+ATpKb5Gs2Pw40go6OP5itcBjMXviOo84m5A@mail.gmail.com>
Σταύρος Ντέντος <stdedos@gmail.com> wrote:
> On Sat, 27 Mar 2021 at 21:32, Eric Wong <e@80x24.org> wrote:
> > It does, it clutters up the directory listing ("homepage").
> > Also redirect adds latency + traffic.
> >
> > If somebody is already looking at public-inbox.org, then "meta/"
> > is already the top link in the listing.
>
> Hmm .... I "skipped" it as some error (why on earth "meta" is first on
> a "name-ascending" sorting?!?!).
It matches nginx behavior, as well as Apache w/ FoldersFirst
option enabled.
> > Fwiw, the test suite runs w/o install.
>
> I wanted to test my change "in reality" (i.e. its browser rendering),
> rather than run a testing suite.
> Honestly, I blacked out after being unable to see my result, I didn't
> think to run tests.
> (especially considering the not-so-big changes done).
Ah, "perl -I lib script/public-inbox-httpd -l $HOST:$PORT"
lets you run on ~/.public-inbox/config, or whatever PI_CONFIG=
you want. When I work on WWW changes, I also use:
plackup -I lib -o 127.0.0.1 -R lib -r examples/public-inbox.psgi
Which does auto-reloading and ensures stuff works on generic
PSGI servers.
> > Agree. Note public-inbox.git has a new "symlink-install" target
> > that allows a minimimum install footprint:
> > [Also], it's in Debian sid, now: https://packages.debian.org/public-inbox
>
> True, but I'd be missing "a backend of existing threads".
> But now that I think of it, I could've just cloned any small enough
> repo (e.g. meta? :-p)
Yes, meta is pretty small, still. There's many smaller v2 ones
at lore: lore.kernel.org tools | workflows | dwarves ...
prev parent reply other threads:[~2021-03-28 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 16:31 [PATCH v1] git-send-email-reply: Append subject 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
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 [this message]
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 \
--in-reply-to=20210328225836.GA17258@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=stdedos@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).