From: Chuck Gelm <nc8q@gelm.net>
To: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Xastir.lsm ?
Date: Thu, 02 Jan 2003 17:30:36 -0500 [thread overview]
Message-ID: <3E14BD8C.1DF51A36@gelm.net> (raw)
In-Reply-To: Pine.LNX.4.33.0301021349170.19643-100000@wapiti.tc.fluke.com
Hi, Curt:
Thanks.
However, my main issue is that I do not want to keep track of
development revisions. My main issue is that I want the 'stable'
version release and the 'stable' files. My original
opinion that I posted here, was that Xastir is developmental
code. Your posts seem to confirm this opinion.
:-|
Happy New Year, Chuck
"Curt Mills, WE7U" wrote:
>
> On Thu, 2 Jan 2003, Chuck Gelm wrote:
>
> > Heh, heh, heh. You think you can trick me into
> > debugging someone's software. ? Think again. ;-)
>
> That's pretty good! I might have to borrow that sometime in the
> future...
>
> > 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?
>
> Think of RCS as being able to tell you what has changed in _one_
> file between revisions. Think of CVS as the same thing but able to
> do it on an entire tree of files instead of just one. That's the
> basic idea.
>
> If you have a large tree of files (like Xastir) and want to check
> the status of your tree against the development tree, you issue one
> command and it will tell you which files have changed. Issue
> another command against a particular file and it will show you the
> diff's. Issue another command ("cvs update") and it will make your
> tree be in sync with the development tree. It's all pretty slick.
> Just don't mess with the "CVS" directories and the bookkeeping files
> contained within, or CVS will get lost. Easy enough to delete the
> entire thing and bring down a fresh tree though in that case.
>
> For the developers it's even slicker, as we can be committing
> changes to different parts of the tree at the same time. Trying to
> change the same file at the same time gets tricky, as the first one
> there gets the lock, and the 2nd is refused. #2 gets to figure out
> how to merge his changes in with the first guy's before CVS will let
> him check his stuff in. A race to the finish!
>
> I've been in races with a developer in Germany before in just this
> scenario. Sometimes he wins, sometimes I do. And you thought
> software coding was just an armchair sport... ;-)
>
> > Is there a Xastir.lsm ?
>
> Don't see one anywhere. We have an xastir.1 and an xastir.spec
> though!
>
> --
> Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
> Senior Methods Engineer/SysAdmin
> "Lotto: A tax on people who are bad at math!"
> "Windows: Microsoft's tax on computer illiterates!" -- WE7U
> "The world DOES revolve around me: I picked the coordinate system!"
next prev parent reply other threads:[~2003-01-02 22:30 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 ` Xastir.lsm ?; was " Chuck Gelm
2003-01-02 21:59 ` Curt Mills, WE7U
2003-01-02 22:30 ` Chuck Gelm [this message]
2003-01-02 22:58 ` Xastir.lsm ? 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=3E14BD8C.1DF51A36@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