From: Eric Wong <e@80x24.org>
To: Philip Oakley <philipoakley@iee.org>
Cc: git@vger.kernel.org
Subject: Re: Mapping old gmane numbers to existing amil servers?
Date: Thu, 11 Aug 2016 22:26:15 +0000 [thread overview]
Message-ID: <20160811222615.GA5607@starla> (raw)
In-Reply-To: <95848D06D55D4633A686DD892D12F501@PhilipOakley>
Philip Oakley <philipoakley@iee.org> wrote:
> The raw download works. My home ISP is currently blocking your email for
> some reason, though I do see it at my work - my iee.org alias is via my
> professional body which duplicates the email when it relays it.
Hmm, do other emails from other users get blocked?
I wonder if it's lack of DKIM (which gets invalidated by the
list sig vger appends) or something else...
> On thing I did note on the web display of the threads is that it would be
> good to have a leader of " . . . . . `" so that one can count the level of
> indent, and see the alignments via the columns of dots.
>
> When looking at
> https://public-inbox.org/git/0648000B273C412AB7140AE959EBC99A%40PhilipOakley/
> I had difficulty working out which email the last 4 were replying to.
https://public-inbox.org/git/0648000B273C412AB7140AE959EBC99A%40PhilipOakley/
So, right now, it's:
2016-07-20 21:10 ` [PATCH v4 8/8] doc: revisions - clarify reachability examples Philip Oakley
2016-07-20 22:22 ` Junio C Hamano
2016-08-11 21:50 ` [PATCH v5 00/12] Update git revisions Philip Oakley
2016-08-11 21:50 ` [PATCH v5 01/12] doc: use 'symmetric difference' consistently Philip Oakley
2016-06-25 19:49 ` Junio C Hamano
2016-06-27 13:37 ` Philip Oakley
2016-06-27 15:08 ` Junio C Hamano
2016-06-27 15:39 ` Philip Oakley
And you would rather see something like:
2016-07-20 21:10 . ` [PATCH v4 8/8] doc: revisions - clarify reachability examples Philip Oakley
2016-07-20 22:22 . ` Junio C Hamano
2016-08-11 21:50 . ` [PATCH v5 00/12] Update git revisions Philip Oakley
2016-08-11 21:50 . ` [PATCH v5 01/12] doc: use 'symmetric difference' consistently Philip Oakley
2016-06-25 19:49 ` Junio C Hamano
2016-06-27 13:37 ` Philip Oakley
2016-06-27 15:08 ` Junio C Hamano
2016-06-27 15:39 ` Philip Oakley
?
Actually, my initial inclination was to use the '|' character
which is what mutt does
2016-07-20 21:10 | } [PATCH v4 8/8] doc: revisions - clarify reachability examples Philip Oakley
2016-07-20 22:22 | } Junio C Hamano
2016-08-11 21:50 | ` [PATCH v5 00/12] Update git revisions Philip Oakley
2016-08-11 21:50 | ` [PATCH v5 01/12] doc: use 'symmetric difference' consistently Philip Oakley
2016-06-25 19:49 ` Junio C Hamano
2016-06-27 13:37 ` Philip Oakley
2016-06-27 15:08 ` Junio C Hamano
2016-06-27 15:39 ` Philip Oakley
It should be doable, and the '`' immediately following the last
'|' probably ought to be a link to the parent, too.
I would also like to use '}' (as above) or '+' where mutt would
use "├─>" or just '├', but I don't think I can introduce multibyte
chars without causing problems for some users.
Anyways, it's definitely on my ever-growing todo list.
(Wow, it is refreshing to be a "web designer" who can live
entirely in a terminal without relying on screenshots :D)
next prev parent reply other threads:[~2016-08-11 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 7:01 Mapping old gmane numbers to existing amil servers? Philip Oakley
2016-08-11 7:56 ` Eric Wong
2016-08-11 21:00 ` Philip Oakley
2016-08-11 22:26 ` Eric Wong [this message]
2016-08-12 7:38 ` Philip Oakley
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160811222615.GA5607@starla \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).