public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas D. Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Major problem with Speakup.
Date: Fri, 17 Aug 2001 20:29:24 -0400	[thread overview]
Message-ID: <017901c1277c$d57dbd60$3590fea9@starbase> (raw)
In-Reply-To: <Pine.LNX.4.33.0108170631210.25549-100000@lnx1.holmesgrown.com>

Hi, Steve. I think that you and I are on the same thought. I merely wanted a
CVS package that was in a single file that could be applied rather than this
checkout on the fly method.
I guess what I am asking is it possible to have both? The current checkout
method, and perhaps a tar ball of the files that can be backed up somewhere,
and applied to the source tree manually?

----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, August 17, 2001 9:35 AM
Subject: Re: Major problem with Speakup.


> This discussion does bring up one question for me though.  Is there a way
> to get the CVS update into a single file and then deal with that in a
> stand alone basis?  I'm not really up on CVS so the only part I'm familiar
> with is its "on the fly patching" of files already on the system.  In the
> case of speakup, I would like to use CVS to get the patches, hold them off
> to the side and then apply them to a new kernel tree whenever I need them.
> Does that make sense?
>
> On Fri, 17 Aug 2001, Kirk Wood wrote:
>
> > WEll things may not b done simply cause Kirk (the other one) is doing
all
> > of this on his own time for no money. Send him enough and he might be
> > quiet happy to provide all kinds of service.
> >
> > As for a way around the situation there is a simple one. Download all
you
> > need from a computer that has an internet connection. Then transfer the
> > data. (You did leave a means for data tranfer didn't you?) I find it
hard
> > to believe nobody has a CD burner that you know of.  In fact, probably
> > someone has a high speed connection and a burner and would do it for the
> > cost of the disk. Ask your friends.
> >
> > The download need not occur on a linux machine. I have downloaded many a
> > file from a windows machine then tranfered to my linux machine. Just
> > transfer in binary mode.
> >
> > =======
> > Kirk Wood
> > Cpt.Kirk@1tree.net
> >
> > The mind is like a parachute; it works much better when open.
> > If you're too open minded, your brains will fall out.
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Thomas D. Ward
 ` Buddy Brannan
   ` Thomas D. Ward
     ` Gregory Nowak
     ` Kirk Wood
       ` Steve Holmes
         ` Thomas D. Ward [this message]
     ` Janina Sajka
     ` Janina Sajka
       ` Thomas D. Ward
         ` Gregory Nowak
           ` using Linux was " Kenny Hitt
         ` Janina Sajka
       ` Gregory Nowak
         ` Scott Howell
           ` Gregory Nowak
             ` Kirk Wood
               ` Gregory Nowak
               ` Brian Borowski
 ` Tommy Moore
   ` Amanda Lee
     ` Thomas D. Ward
       ` Amanda Lee
 ` Gene Collins
 ` William F. Acker WB2FLW +1-303-777-8123
   ` Thomas D. Ward
     ` William F. Acker WB2FLW +1-303-777-8123
       ` Thomas D. Ward
         ` Gregory Nowak

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='017901c1277c$d57dbd60$3590fea9@starbase' \
    --to=tward@bright.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).