kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ruben@mrbrklyn.com (Ruben Safir)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Developing environments used for kernel development
Date: Thu, 24 Dec 2015 19:29:11 -0500	[thread overview]
Message-ID: <567C8DD7.90104@mrbrklyn.com> (raw)
In-Reply-To: <178393.1450982607@turing-police.cc.vt.edu>

On 12/24/2015 01:43 PM, Valdis.Kletnieks at vt.edu wrote:
> The only *real* fix is to go to a non-querty keyboard. 


No, retraining and reprogramming the user is not a solution.



-- 
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com

Being so tracked is for FARM ANIMALS and and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013

  parent reply	other threads:[~2015-12-25  0:29 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 19:27 Developing environments used for kernel development Daniel.
     [not found] ` <CAJX_Q+2AOXLM=XWsSYzUbpG=MKH+p2D1Xf2k7xGFrQdn=_zPTQ@mail.gmail.com>
2015-12-22 21:26   ` Daniel.
2015-12-22 21:43     ` Lucas Tanure
2015-12-22 22:41       ` Daniel.
2015-12-22 22:15     ` Clemens Gruber
2015-12-23  0:06       ` Daniel.
2015-12-24 11:59         ` Andrey Skvortsov
2015-12-24 13:57           ` Daniel.
2016-01-14  0:23             ` Ismael Luceno
2016-01-14  0:37               ` Geyslan G. Bem
2016-01-14 13:06                 ` Daniel.
2016-01-14 13:53                   ` Geyslan G. Bem
2016-01-14 14:26                   ` Geyslan G. Bem
2016-01-14 15:23                     ` Daniel.
2016-01-14 15:35                       ` Geyslan G. Bem
2016-01-14 16:28                         ` Daniel.
2016-01-14 16:28                           ` Daniel.
2016-01-14 16:36                             ` Geyslan G. Bem
2016-01-14 16:52                             ` Daniel.
2016-01-14 16:58                               ` Geyslan G. Bem
2015-12-24 15:41           ` Ruben Safir
2015-12-24 17:33             ` Daniel.
2015-12-24 18:43             ` Valdis.Kletnieks at vt.edu
2015-12-24 20:13               ` Manuel Pégourié-Gonnard
2015-12-25  0:29               ` Ruben Safir [this message]
2015-12-25  0:52                 ` Valdis.Kletnieks at vt.edu
2015-12-25  1:42                   ` Ruben Safir
     [not found] ` <4E5779AD88B2F040B8A7E83ECF544D1A64AC5F@SJCPEX01CL03.citrite.net>
2015-12-23  1:18   ` Daniel.
2015-12-23 13:30     ` Daniel.
2015-12-23 14:45       ` amit mehta
2015-12-23 17:20         ` Daniel.
2016-01-14 19:19     ` Geyslan G. Bem
2016-01-14 20:08       ` Daniel.
2015-12-25 17:14 ` Raymond Jennings
2015-12-28 12:28   ` Daniel.
2015-12-28 12:57     ` Manuel Pégourié-Gonnard
2015-12-28 14:05       ` Fernando Apesteguía
2015-12-28 19:11         ` Daniel.
2015-12-29  5:10           ` Daniel.
2015-12-29  9:50             ` Manuel Pégourié-Gonnard

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=567C8DD7.90104@mrbrklyn.com \
    --to=ruben@mrbrklyn.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).