public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: espeakup v0.4 released
Date: Wed, 22 Oct 2008 20:33:40 -0500	[thread overview]
Message-ID: <20081023013339.GA23530@linux1> (raw)
In-Reply-To: <20081023012156.GA8406@lnx3.holmesgrown.com>

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

This is fixed now; when I do a push to the speakup repository, it
commits to the one on bumpy, but mine updates every few hours.  I just
forced an update.

Thanks,

William

On Wed, Oct 22, 2008 at 06:21:57PM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> When I do a git-pull, it keeps saying all files are up to date.  But
> when I look in the contrib directory, 0.3 is still there.  Below is
> where git is pulling from.
> 
> url = git://hubbs.homedns.org/speakup.git
> 
> On Wed, Oct 22, 2008 at 07:38:35PM -0500, William Hubbs wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > All,
> > 
> > I just released espeakup v0.4, and it is available in the contrib
> > directory of the speakup git repository.  Here is a quick list of
> > changes:
> > 
> >       removed the callback function - this fixes the issue with espeakup
> >       taking a while to stop speaking.
> > 
> >       fixed an off-by-one error
> >       made the synth flush character a constant for readability
> >       Fixed the select call
> >       the main loop now uses strrchr and strcpy
> >       changed process_buffer to use the isprint() call.
> >       changed strcpy to memmove
> >       fixed the number of bytes to move in the memmove() call
> >       fixed the length calculation when a flush is processed.
> >       Revert "fixed the length calculation when a flush is processed."
> >       fixed the makefile
> >       moved all variable definitions to the top of the Makefile.
> >       Added support for the punctuation command from speakup
> >       fixed a bug in process_command
> >       Released v0.4.
> > 
> > If you have any questions, please let me know.
> > 
> > Thanks,
> > 
> > William
> > 
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.9 (GNU/Linux)
> > 
> > iEYEARECAAYFAkj/x4sACgkQblQW9DDEZTjJGACffFS+iK0WGcNVlnc3ET+RtlQq
> > 2pIAn3dh6FxPGG10TY7/s7Sjwwd7mfpy
> > =KUW3
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> 
> iEYEAREDAAYFAkj/0bQACgkQWSjv55S0LfHlAQCgi6DZTVLQr3VQnZnc4rdVOBFE
> il4AnRDyI8pidm0c2rbbd7pjvNZAvW2q
> =Iuk0
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkj/1HMACgkQblQW9DDEZThnKgCcDJR64+EF5fab1IACySv5pG4G
MyMAn35KWJW32ybb4Rf5zTI71dW+SgNj
=4PCr
-----END PGP SIGNATURE-----

  reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 William Hubbs
 ` Steve Holmes
   ` William Hubbs [this message]
     ` Steve Holmes

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=20081023013339.GA23530@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).