git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Eric Wong" <e@80x24.org>
Cc: <git@vger.kernel.org>
Subject: Re: Mapping old gmane numbers to existing amil servers?
Date: Fri, 12 Aug 2016 08:38:24 +0100
Message-ID: <6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley> (raw)
In-Reply-To: <20160811222615.GA5607@starla>

From: "Eric Wong" <e@80x24.org>
Sent: Thursday, August 11, 2016 11:26 PM
> 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...

Not really sure. My professional body's alias service now uses EveryCloud 
for its antispam. initially it also blocked your mails as 'spam', by the 
daily notification allows me to white list that. However the forwarded 
emails go to both home & work, and only the home ISP (cheap but annoying) 
then has no white list mechanism and no way of seeing what they binned.

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

Not quite, 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


I haven't filled in the last ones because there are no matching follow on 
replies, e.g to Junio' s 2016-06-25 19:49 message.
(I may not have put in enough of the lead either)
However for ease of formatting I guess that simply setting the indent to be 
'. ' rather than '  ' (both 2 chars) would create the impression of the 
messages being on an indent grid

If rather than looking at those below junio's reply, you try and look at 
which message he was replying to, it's very hard (It's more than a full 
screen scroll up), hance the request for the alignment 'column of dots'. I 
think he was replying to my 2016-06-25 13:50, but it's not easy to be sure.

> ?
>
> 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 feel that the '¦' style chars will fill the screen too much (with '.' 
being the minimalist I can think of), but it's a personal choice.

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

Philip 


      reply index

Thread overview: 5+ messages in thread (expand / mbox.gz / Atom feed / [top])
2016-08-11  7:01 Philip Oakley
2016-08-11  7:56 ` Eric Wong
2016-08-11 21:00   ` Philip Oakley
2016-08-11 22:26     ` Eric Wong
2016-08-12  7:38       ` Philip Oakley [this message]

Reply instructions:

You may reply publically 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 to all the recipients using the --to, --cc,
  and --in-reply-to switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E3699DEA672430CAEA6DEFEDE6918F4@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.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

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox