From: Paul Mackerras <paulus@samba.org>
To: Dinar valeev <k0da@opensuse.org>
Cc: linuxppc-dev@ozlabs.org, aik@ozlabs.ru,
nikunj@linux.vnet.ibm.com, thuth@redhat.com,
Dinar Valeev <dvaleev@suse.com>
Subject: Re: [PATCH v2] Caps in not always shift
Date: Fri, 10 Jul 2015 16:42:39 +1000 [thread overview]
Message-ID: <20150710064238.GB19196@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1436374064-4116-1-git-send-email-k0da@opensuse.org>
On Wed, Jul 08, 2015 at 06:47:44PM +0200, Dinar valeev wrote:
> From: Dinar Valeev <dvaleev@suse.com>
>
> Caps behaves like shift only for latin characters.
> In case we're typing - for example with caps enabled, SLOF picks _ char
> from shifted table.
>
> Threat caps as shift only for letters.
"Treat" not "Threat".
And I suggest you make the subject "Caps is ..." rather than
"Caps in ...".
Paul.
next prev parent reply other threads:[~2015-07-10 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 16:47 [PATCH v2] Caps in not always shift Dinar valeev
2015-07-09 6:00 ` Thomas Huth
2015-07-09 12:59 ` Segher Boessenkool
2015-07-10 6:42 ` Paul Mackerras [this message]
2015-07-13 10:11 ` Dinar Valeev
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=20150710064238.GB19196@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=aik@ozlabs.ru \
--cc=dvaleev@suse.com \
--cc=k0da@opensuse.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=thuth@redhat.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 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).