From: "ace" <ace@talkingirc.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Patch hunk rejection?
Date: Tue, 26 Jun 2007 11:26:35 -0400 [thread overview]
Message-ID: <24F0D6478C1A4D6C856E5DAF029DFC76@Michelle> (raw)
In-Reply-To: <BAY141-DAV1334301F98FE27C9BDD9588F0B0@phx.gbl>
You really ought to just get the latest 2.6.21.x kernel and build it from
scratch that way. It may take some tweeking but you'll thank yourself in
the end. Good experience.
If you plan on updating your kernel frequently, get the linux-2.6.21.tar.bz2
file along with the latest patch for that kernel, like linux-2.6.21.5.patch
and apply it. Then, when a new patchlevel comes out, get that new patch,
linux-2.6.21.6.patch, unapply the patchlevel 5 patch and apply 6.
----- Original Message -----
From: "Zachary Kline" <Z_kline@hotmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, June 26, 2007 2:37 AM
Subject: Patch hunk rejection?
> 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
>
>
> __________ NOD32 2355 (20070626) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
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 [this message]
` Gregory Nowak
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=24F0D6478C1A4D6C856E5DAF029DFC76@Michelle \
--to=ace@talkingirc.net \
--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).