public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: Scroll lock bug
Date: Mon, 16 Jun 2008 19:25:06 -0500	[thread overview]
Message-ID: <20080617002506.GA22761@linux1> (raw)
In-Reply-To: <20080616212554.GC4876@implementation>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Luke,

On Mon, Jun 16, 2008 at 10:25:54PM +0100, Samuel Thibault wrote:
> luke, le Mon 16 Jun 2008 15:49:16 -0400, a ?crit :
> > On Mon, 16 Jun 2008, Samuel Thibault wrote:
> > 
> > > luke, le Mon 16 Jun 2008 04:17:15 -0400, a ?crit :
> > > > It solves that problem, which creates another, far worse.
> > > > Particularly, all review key functions behave with intolerable slowness.  
> > > 
> > > Could you try 
> > > git checkout 28b0bfd7
> > > to make sure that you are getting the fix for scroll lock, and not a
> > > more recent change that involved flush?
> > 
> > I'm working on that compile now.
> > Question: short of cloning again (which I'm fine with) how do I recover to 
> > the current version after this is over?
> 
> git checkout master
 
Also, can you send the .config file you used to build this kernel off
list to myself and Samuel?

Thanks,

William

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkhXBGIACgkQblQW9DDEZTh5zACfX7QMcIKodch3eLokxLlAJHPu
JqAAoLO59bJNRUog/ZX1DMu+np42Ray4
=vHjN
-----END PGP SIGNATURE-----

  reply	other threads:[~ UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 luke
 ` Samuel Thibault
   ` Samuel Thibault
     ` luke
       ` Samuel Thibault
         ` luke
         ` luke
           ` Samuel Thibault
             ` William Hubbs [this message]
         ` luke
           ` Samuel Thibault
             ` Probable flush update problem in source luke
           ` Scroll lock bug Samuel Thibault
             ` luke
             ` luke

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=20080617002506.GA22761@linux1 \
    --to=w.d.hubbs@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).