Minor: fix for CVS/Aegis instructions

http://www.bestpractical.com/rt/cvs.html is very out of date. Where it
says:

RT 2.0 lives on a branch called “rt-2-0”. Get your hot fresh source
at:
cvs -d :pserver:anoncvs@cvs.fsck.com:/raid/cvsroot co -r rt-2-0 rt

The current development sources live on the repository’s HEAD
cvs -d :pserver:anoncvs@cvs.fsck.com:/raid/cvsroot co rt
cvs -d :pserver:anoncvs@cvs.fsck.com:/raid/cvsroot co DBIx

it should instead say something like:

RT 2.0.x development is in the cvs HEAD branch. Get your hot fresh
source at:
cvs -d :pserver:anoncvs@cvs.fsck.com:/raid/cvsroot co rt

Actually, RT 2.0.x development is done in Aegis, but exported to cvs.
RT 2.1.x development is done only with Aegis, see

 http://fsck.com/aegis/aegis.cgi?file@proj_menu+project@rt.2.1

and work it out from there.

(and I’m not subscribed to this mailing list very often.)

Dan

Actually, RT 2.0.x development is done in Aegis, but exported to cvs.
RT 2.1.x development is done only with Aegis, see

 http://fsck.com/aegis/aegis.cgi?file@proj_menu+project@rt.2.1

and work it out from there.

Wow. You guys just went up a notch in my book.

-Robin

http://www.digitalkingdom.org/~rlpowell/ BTW, I’m male, honest.
le datni cu djica le nu zifre .iku’i .oi le so’e datni cu to’e te pilno
je xlali – RLP http://www.lojban.org/

Actually, RT 2.0.x development is done in Aegis, but exported to cvs.

Well, 2.0 development is done in CVS. 2.1 is being done in aegis.
The cvs export tools are still somewhat flaky, but they’re getting there.
Thanks for the doc updates, Dan.

We’re not yet using all the cool stuff that aegis lets us do (And some of
it, we may never use; aegis’ testing methodology doesn’t map well to
perl’s Test::Inline, for instance) but overall, I’m quite happy. I can
finally develop and checkin on my laptop, when I’m netless. and then I
can commit upstream and preserve the version history. In the distant
future, I’ve got visions of a tight integration of aegis and RT. Imagine,
if you will, an “Apply Patch” button in RT. :slight_smile:

-jesse

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

Actually, RT 2.0.x development is done in Aegis, but exported to cvs.
RT 2.1.x development is done only with Aegis, see

 http://fsck.com/aegis/aegis.cgi?file@proj_menu+project@rt.2.1

and work it out from there.

(and I’m not subscribed to this mailing list very often.)

Dan

why did you use aegis instead of cvs?

Thanks

marc

This was discussed on rt-dev in February 2002. See this thread for more
info: http://lists.fsck.com/pipermail/rt-devel/2002-February/002005.html .
Search the archive for the exact reasons:
http://lists.fsck.com/cgi-bin/htsearch . Quite an extensive discussion
took place on that list over the course of several weeks.

Regards,
George-----Original Message-----
From: Marc Spitzer [mailto:marc@cv.net]
Sent: Monday, May 06, 2002 11:19 AM
To: Dan Shearer
Cc: rt-users@lists.fsck.com
Subject: Re: [rt-users] Minor: fix for CVS/Aegis instructions

On Sat, 04 May 2002 11:03:58 +0930 (CST) Dan Shearer dan@tellurian.com.au wrote:

Actually, RT 2.0.x development is done in Aegis, but exported to cvs.
RT 2.1.x development is done only with Aegis, see

 http://fsck.com/aegis/aegis.cgi?file@proj_menu+project@rt.2.1

and work it out from there.

(and I’m not subscribed to this mailing list very often.)

Dan

why did you use aegis instead of cvs?

Thanks

marc

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

This email message may contain information that is confidential and
proprietary to Babcock & Brown or a third party. If you are not the
intended recipient, please contact the sender and destroy the original and
any copies of the original message. Babcock & Brown takes measures to
protect the content of its communications. However, Babcock & Brown cannot
guarantee that email messages will not be intercepted by third parties or
that email messages will be free of errors or viruses.

Actually, RT 2.0.x development is done in Aegis, but exported to cvs.
RT 2.1.x development is done only with Aegis, see

 http://fsck.com/aegis/aegis.cgi?file@proj_menu+project@rt.2.1

why did you use aegis instead of cvs?

Jesse’s reasons behind Aegis are given in the rt-devel archives.

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations