public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: a note for those patching 2.6.18 with current cvs
Date: Wed, 27 Sep 2006 20:23:25 -0700	[thread overview]
Message-ID: <20060928032325.GA23572@localhost.localdomain> (raw)

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

Hi all.

Since I'm currently in the process of upgrading to linux 2.6.18, I
thought I'd post this note for anyone who wants to patch current
speakup from cvs in to a 2.6.18 kernel, but doesn't know how to go
about doing that.

First, according to the cvs mailing list, the patches for 2.6.18 were
submitted into the speakup cvs on August 14th, in the evening
EDT. Checking out cvs as of August 15th has patched for me into 2.6.18
without problems.

Now that we know that, you'll need to modify the checkout script. If
you don't want to mess with your current checkout script, then make a
copy of it somewhere else.

In the checkout script, you want to find the line that reads:

cvs co -P speakup || exit

and I've replaced that line with:

cvs co -D 'August 15 2006' -P speakup || exit

, which worked for me, though you can use any of the allowed date
formats as out-lined in the cvs manual. Then, just run the checkout
script in the way you'd normally run it. Hth some folks.

Greg


- -- 
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.5 (GNU/Linux)

iD8DBQFFG0At7s9z/XlyUyARAnB3AKC7PmNIUArEpG8Wy4D9pYqC52a9pQCbBpKs
qNSdKzO6kCTWaT+9lx83UWg=
=Urt6
-----END PGP SIGNATURE-----


             reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gregory Nowak [this message]
 ` Garrett Klein
 ` Austin Seraphin
 ` Luke Davis
   ` Luke Davis
     ` Chuck Hallenbeck

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=20060928032325.GA23572@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).