From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Patch hunk rejection?
Date: Tue, 26 Jun 2007 09:36:32 -0700 [thread overview]
Message-ID: <20070626163632.GA11296@localhost.localdomain> (raw)
In-Reply-To: <BAY141-DAV1334301F98FE27C9BDD9588F0B0@phx.gbl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This is to be expected, current speakup cvs will not patch into
anything lower then 2.6.20 I believe. You need to either checkout cvs
from an earlier date, or just go for 2.6.21.5.
Greg
On Mon, Jun 25, 2007 at 11:37:28PM -0700, Zachary Kline wrote:
> Hiya,
> Doug, when I tried to apply Speakup patches to the kernel 2.6.17 I downloaded from Slackware, I got a couple of messages about hunk rejections. They occured in keyboard.c and vt.c. I was wondering if these were well-understood problems with the patch, or are just a sign that I do indeed need to use 2.6.21.5 or something like that without relying on a Slackware package?
> Thanks,
> Zack.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGgUCQ7s9z/XlyUyARAkVvAKDZ4EpExhmxf1Fc7bCFbyY4gjvaTQCcD1Pv
V0cioj/odHji8bUHHsSYJEw=
=Za6w
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Doug Sutherland
` ace
` Gregory Nowak [this message]
Doug Sutherland
` Zachary Kline
` Adam Myrow
` Gregory Nowak
` Doug Sutherland
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=20070626163632.GA11296@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).