On Thu, Oct 18, 2018 at 12:03 PM Simo Sorce <simo@redhat.com> wrote:
On Thu, 2018-10-18 at 11:51 -0700, Gerald B. Cox wrote:
> On Thu, Oct 18, 2018 at 11:40 AM Simo Sorce <simo@redhat.com> wrote:
>
> > On Wed, 2018-10-17 at 11:02 -0700, Gerald B. Cox wrote:
> > > On Wed, Oct 17, 2018 at 10:55 AM Samuel Sieb <samuel@sieb.net> wrote:
> > >
> > > > On 10/17/18 8:52 AM, Gerald B. Cox wrote:
> > > > > Again, I use gmail and things look perfectly fine for me.
> > > >
> > > > That's because gmail only shows the HTML part.
> > > >
> > >
> > > Ah... so it's a client issue.  Good to know.
> >
> > No it is a service issue that just happen not to affect *your* client
> > of choice. There is a big difference.
> >
> > Simo.
> >
>
> You need to read the entire thread in context, including subsequent
> responses.  I realize that can be difficult on a mailing list, with
> all the top-posting, conversation snippets, etc.

I did read the thread, and there is no difficulty at all to read a
thread, given my client can do threading just fine, the comment stands.

Well, maybe you need to read it again - because you're missing the point.