CVS commit add-on

How useful is the CVS commit add-on? I mean, I think it will be very useful
if we get stuck using CVS. :wink: However, should I use it (a strong tie-in
between CVS and rt) as a ‘plus’ for CVS?

rob

How useful is the CVS commit add-on? I mean, I think it will be very useful
if we get stuck using CVS. :wink: However, should I use it (a strong tie-in
between CVS and rt) as a ‘plus’ for CVS?

Sorry about that. This belongs on rt-users. Going there now.

ob

How useful is the CVS commit add-on? I mean, I think it will be very useful
if we get stuck using CVS. :wink:

I find it very useful when working with CVS, but I’m the author so I’m
supposed to say that.

However, should I use it (a strong tie-in between CVS and rt) as a ‘plus’ for CVS?

Well, there’s no reason an equivalent couldn’t get written for any other version
control system. Whatever I move RT development to will likely get a similar
script or set of scripts. If you need something now or are looking at moving
to something other than what I eventually pick, I’d be happy to talk to you
about putting together an equivalent handler for your version control
system of choice.

-j

rob


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

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

How useful is the CVS commit add-on? I mean, I think it will be very useful
if we get stuck using CVS. :wink: However, should I use it (a strong tie-in
between CVS and rt) as a ‘plus’ for CVS?

rob

We are using this script since its first announce by Jesse. It has only one
disadvantage - we are not able to enter working time with it. All the rest
are only “pluses”.
The most lovely thing is that we always have definite connection between
ticket and all modification made.