Re: automating cvs checkout/checkin and also don't checkin identical files
Yes, that's exactly what I'm going to do. I meant to say custom Ant TARGET, not TASK. Thanks! Chad Eric Siegerman wrote: On Tue, Dec 16, 2003 at 06:03:30PM -0700, Chad Woolley wrote: I can now write a custom Ant task to commit all files, without worrying which have been modified. Have you looked at the cvs core task? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: automating cvs checkout/checkin and also don't checkin identical files
Eric Siegerman wrote: You'll have to explain a bit more what you mean, I think. I'm looking to automate this via Apache Ant. Also, on the checkin, I don't want to check in any files that have identical contents to the repository version - even if they have been saved with a new timestamp. This is how CVS already works. Thanks, I never realized that. I thought I had to manually ignore the identical files. I think that's all I really needed to know. I can now write a custom Ant task to commit all files, without worrying which have been modified. Thanks for your help. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
automating cvs checkout/checkin and also don't checkin identical files
Hi, This may be a bit off topic, but maybe someone can help. I am looking for a way to automate a CVS checkout/checkin process. Also, on the checkin, I don't want to check in any files that have identical contents to the repository version - even if they have been saved with a new timestamp. Thanks, Chad ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: automating cvs checkout/checkin and also don't checkin identical files
On Mon, Dec 15, 2003 at 09:20:45PM -0700, Chad Woolley wrote: I am looking for a way to automate a CVS checkout/checkin process. You'll have to explain a bit more what you mean, I think. Also, on the checkin, I don't want to check in any files that have identical contents to the repository version - even if they have been saved with a new timestamp. This is how CVS already works. If you're working client/server, CVS will tell you in its log-message-editor comments that the file is modified, but it won't actually check in a new revision. That little mislead happens because at the time CVS collects the log message, it knows which files have different timestamps, but doesn't yet know which subset of them also have different content. (It can't diff the files until it's sent the sandbox copy to the server (duh), and it can't do that until it has the log message, because it needs to send all data necessary for the commit to the server in one go, without any pauses for user interaction.) When operating locally, on the other hand, it can figure that out *before* collecting log messages, so it can display an accurate file list. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
