From: Chuck Gelm <nc8q@gelm.net>
To: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Cc: linux-hams@vger.kernel.org
Subject: Xastir.lsm ?; was Re: Writing AX.25 Server Progie
Date: Thu, 02 Jan 2003 16:38:31 -0500 [thread overview]
Message-ID: <3E14B157.9B1C1CD6@gelm.net> (raw)
In-Reply-To: Pine.LNX.4.33.0301021052220.18470-100000@wapiti.tc.fluke.com
"Curt Mills, WE7U" wrote:
>
> On Wed, 1 Jan 2003, Chuck Gelm wrote:
>
> > Thanks for your informative response.
> > I'll try a 'stable' release of Xastir soon.
>
> No! Try the latest "development" package instead! :-)
Heh, heh, heh. You think you can trick me into
debugging someone's software. ? Think again. ;-)
> > However, I have no idea what CVS is.
> > Is CVS are requirement?
>
> _I_ think it is! ;-)
>
> CVS stands for Concurrent Versions System. It's built on top of
> RCS, so you need both installed.
So, now I need RCS too! :-(
I think that RCS is Revision Control System.
Why would I need to keep track of someone else's revisions?
Oh, never mind that.
Is there a Xastir.lsm ?
Chuck
<snipped to end>
next prev parent reply other threads:[~2003-01-02 21:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 6:07 Writing AX.25 Server Progie Kelly Black
2002-12-31 2:31 ` M Taylor
2002-12-31 16:35 ` Curt Mills, WE7U
2002-12-31 19:02 ` Kelly Black
2002-12-31 23:13 ` Chuck Gelm
2002-12-31 23:43 ` Curt Mills, WE7U
2003-01-01 17:45 ` Chuck Gelm
2003-01-02 19:02 ` Curt Mills, WE7U
2003-01-02 19:13 ` John Ackermann N8UR
2003-01-02 19:33 ` Curt Mills, WE7U
2003-01-02 19:15 ` John Ackermann N8UR
2003-01-02 21:38 ` Chuck Gelm [this message]
2003-01-02 21:59 ` Xastir.lsm ?; was " Curt Mills, WE7U
2003-01-02 22:30 ` Xastir.lsm ? Chuck Gelm
2003-01-02 22:58 ` Curt Mills, WE7U
2003-01-01 7:30 ` Writing AX.25 Server Progie Wilbert Knol
2003-01-01 16:29 ` Kelly Black
2003-01-06 3:02 ` Dennis Boone
2003-01-06 3:39 ` Kelly Black
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=3E14B157.9B1C1CD6@gelm.net \
--to=nc8q@gelm.net \
--cc=hacker@tc.fluke.com \
--cc=linux-hams@vger.kernel.org \
/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