From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: plagnioj@jcrosoft.com, tomi.valkeinen@ti.com, jslaby@suse.cz,
gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] console: Add persistent scrollback buffers for all VGA consoles
Date: Wed, 23 Nov 2016 17:21:56 +0000 [thread overview]
Message-ID: <1479921716.5446.4.camel@gmx.de> (raw)
In-Reply-To: <20161122193143.GG11418@dell-m4800.home>
On Di, 2016-11-22 at 19:31 +0000, Andrey Utkin wrote:
> I'm not sure my emails with review of previous submission reached you, but in
> them I meant to mention that there are some style nits which are easy to
> eliminate.
I am afraid I did not get it. I will fix these style issues in the next
patch: Adam Borowski found another issue with clearing the scrollback
buffer, which I am finally able to reproduce.
> P. S. Manuel, please fix your git-send-email workflow or apply some
> workaround (check locale settings and such). Again your References
> header contains illegal symbol:
>
> References: <201611210615.PPE1zXiO??ngguang.wu@intel.com>
I finally found out where the issue came from: Evolution somehow
reinterprets the Message-Id when you are copying it to the clipboard.
WARNING: multiple messages have this Message-ID (diff)
From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: plagnioj@jcrosoft.com, tomi.valkeinen@ti.com, jslaby@suse.cz,
gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] console: Add persistent scrollback buffers for all VGA consoles
Date: Wed, 23 Nov 2016 18:21:56 +0100 [thread overview]
Message-ID: <1479921716.5446.4.camel@gmx.de> (raw)
In-Reply-To: <20161122193143.GG11418@dell-m4800.home>
On Di, 2016-11-22 at 19:31 +0000, Andrey Utkin wrote:
> I'm not sure my emails with review of previous submission reached you, but in
> them I meant to mention that there are some style nits which are easy to
> eliminate.
I am afraid I did not get it. I will fix these style issues in the next
patch: Adam Borowski found another issue with clearing the scrollback
buffer, which I am finally able to reproduce.
> P. S. Manuel, please fix your git-send-email workflow or apply some
> workaround (check locale settings and such). Again your References
> header contains illegal symbol:
>
> References: <201611210615.PPE1zXiO??ngguang.wu@intel.com>
I finally found out where the issue came from: Evolution somehow
reinterprets the Message-Id when you are copying it to the clipboard.
next prev parent reply other threads:[~2016-11-23 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1479832909-19646-1-git-send-email-manuel.schoelling@gmx.de>
[not found] ` <1479832909-19646-3-git-send-email-manuel.schoelling@gmx.de>
2016-11-22 19:31 ` [PATCH v6 2/2] console: Add persistent scrollback buffers for all VGA consoles Andrey Utkin
2016-11-23 17:21 ` Manuel Schölling [this message]
2016-11-23 17:21 ` Manuel Schölling
2016-11-22 16:43 [PATCH v6 0/2] " Manuel Schölling
2016-11-22 16:43 ` [PATCH v6 2/2] " Manuel Schölling
2016-11-22 16:43 ` Manuel Schölling
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=1479921716.5446.4.camel@gmx.de \
--to=manuel.schoelling@gmx.de \
--cc=andrey_utkin@fastmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.