user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Σταύρος Ντέντος" <>
Cc: Eric Wong <>
Subject: Re: [PATCH v1] git-send-email-reply: Append subject
Date: Sun, 28 Mar 2021 19:00:14 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210327193232.GA11329@dcvr>

On Sat, 27 Mar 2021 at 21:32, Eric Wong <> wrote:
> It does, it clutters up the directory listing ("homepage").
> Also redirect adds latency + traffic.
> If somebody is already looking at, 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?!?!).

> > Yeah, me too :-D
> > Having a more clean deploy&isolation&remove process would facilitate
> > in me testing more
> > and providing a cleaner patchset to you.
> 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).

> Agree.  Note public-inbox.git has a new "symlink-install" target
> that allows a minimimum install footprint:
> [Also], it's in Debian sid, now:

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)

  reply	other threads:[~2021-03-28 16:00 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]   ` <>
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               ` Σταύρος Ντέντος [this message]
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='Re: [PATCH v1] git-send-email-reply: Append subject' \

* 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:

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