On środa 12 marzec 2003 08:36 am, Andre Poenitz wrote: > On Wed, Mar 12, 2003 at 08:40:04AM -0500, Kuba Ober wrote: > > No sarcasm intended, but I'd drop CVS and switch to Aegis. I'm using > > Aegis and it does exactly what you're looking for. > > We used Aegis a couple of years ago and I don't remember feeling more > comfortable with it than with CVS...
First of all, Aegis evolves, and recently it even got a few "low karma" (but user-demanded) things implemented, like actually reverting a committed change from the database (the model it implements doesn't really need reverting changes -- a change revert is in most cases just another change that one commits). I guess that one has to have an attitude of burning bridges behind oneself in order to really enjoy Aegis. I had the pleasure of not having a VCS at all in my development, and starting right on with Aegis. I imagine that the CVS legacy may hurt, since your previous experience sort of limits your field of view -- you don't see things that Aegis makes possible. I, for one, find that there's a ton of things that Aegis just does almost by itself, whereas CVS needs some scripting in order to do that. [I do have to use CVS at times for outside development]. As I'm just a VCS user, not a VCS developer, one can understand my reluctance to code VCS managing scripts ;-). And note that Aegis is more than a VCS, whereas CVS is nothing more, and even less at times ;-) Alas, I guess CVS is there to stay. Just like the equally dreaded autotools and Microsoft :) Have a fine time! Cheers, Kuba Ober
