> Yes, that would work. I suppose the question boils down to, what > semantics do you want to associate with 'cvs update'? Your way, every > 'cvs update' implies "I trust this new code and wish to use it in all > projects". I don't think that's *always* what people think when they do > an update. Maybe they just want to look at the code, not use it. Maybe > they're just creatures of habit like me and unthinkingly type 'cvs > update' before starting any work.
I have a shell script being run in every startup that updates all CVS modules I'm currently working with/on, then runs ant against all of them. After my coffee, my email, my sandwich and my daily news gathering, it's usually done and I start work. Every single module in there that makes this not work, I dislike...it is nice not having to start your day thinking about who broke what and why =) > I think the semantics of 'cvs update' should be "synch these files with > the repository"; nothing more. Then an extra step, 'ant dist.lite', > means "I trust this code enough to want to use it in other projects". A big "me too" here! - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
