stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Joachim <svenjoac@gmx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: Major Hayden <major@redhat.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ❎ FAIL: Stable queue: queue-5.0
Date: Tue, 30 Apr 2019 20:44:28 +0200	[thread overview]
Message-ID: <87pnp3fi43.fsf@turtle.gmx.de> (raw)
In-Reply-To: <20190430155827.GC6937@sasha-vm> (Sasha Levin's message of "Tue, 30 Apr 2019 11:58:27 -0400")

On 2019-04-30 11:58 -0400, Sasha Levin wrote:

> On Tue, Apr 30, 2019 at 10:17:17AM -0500, Major Hayden wrote:
>>On 4/30/19 9:01 AM, Greg KH wrote:
>>> On Tue, Apr 30, 2019 at 09:41:59AM -0400, Sasha Levin wrote:
>>>> On Tue, Apr 30, 2019 at 03:27:00PM +0200, Greg KH wrote:
>>>>> On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
>>>>>> Hello CKI folks,
>>>>>>
>>>>>> A minor nit: the icon added before the subject text gets filtered out on
>>>>>> the textual email clients most of us use, and ends up appearing (at
>>>>>> least for me) as 3 spaces that cause much annoyance since it gets
>>>>>> confused with mail threading.

If you see 3 spaces rather than just one, you probably use a single-byte
locale (e.g. 'C'), rather than a UTF-8 one.

>>>>> Really?  It's just a "normal" emoji character, perhaps you need a better
>>>>> email client or terminal window?  :)
>>>>>
>>>>> What are you using that you can't see this in a terminal?
>>>> Um, mutt on xterm...
>>> Use a "modern" terminal program please, that's the problem here.  I just
>>> tried 4 different ones (gnome-terminal, terminology, tilix, and kitty),
>>> and they all worked just fine.
>>>
>>> With mutt :)
>>
>>We can change the email format very easily. If removing the emoji in
>> the subject line would be better, that's a really quick change for
>> us.
>>
>>Our hope was that it would make it easier to identify automated CI
>> results and make it easier to know the feedback when you're looking
>> at a lot of email threads.
>
> I thought this was an issue for more people than just me. I'll just use
> a newer terminal emulator :)

Or configure xterm correctly.  The '❎'emoji displays just fine under
"LC_ALL=en_US.UTF-8 xterm -fa DejaVuSansMono" (tested with xterm 344).

Cheers,
       Sven

  reply	other threads:[~2019-04-30 18:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 12:32 ❎ FAIL: Stable queue: queue-5.0 CKI Project
2019-04-30 12:35 ` Major Hayden
2019-04-30 13:03   ` Sasha Levin
2019-04-30 13:27     ` Greg KH
2019-04-30 13:41       ` Sasha Levin
2019-04-30 14:01         ` Greg KH
2019-04-30 15:17           ` Major Hayden
2019-04-30 15:58             ` Sasha Levin
2019-04-30 18:44               ` Sven Joachim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-06 11:16 CKI Project
2019-05-06 11:26 ` Veronika Kabatova
2019-05-06 12:36   ` Greg KH
2019-05-02 12:32 CKI Project
2019-05-02 12:39 ` Major Hayden
2019-05-02 14:08   ` Greg KH
2019-04-29 13:36 CKI Project
2019-04-29 12:50 CKI Project
2019-04-29 12:38 CKI Project
2019-04-29 12:42 ` Major Hayden
2019-04-29 13:10   ` Greg KH
2019-04-29 12:37 CKI Project
2019-04-04 18:00 CKI Project

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

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

  git send-email \
    --in-reply-to=87pnp3fi43.fsf@turtle.gmx.de \
    --to=svenjoac@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=major@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@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
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 NNTP newsgroup(s).