Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Yeah, if I could ask, I would strongly prefer do not commit in not changed files. (We already have a big trouble with a plenty of null-delta-commits produced by back and forth merging.) JP > -----Original Message----- > From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf > Of Torsten Martinsen > Sent: Thursday, March 31, 2005 15:00 > To: CVSNT > Subject: [cvsnt] BUG: Null delta commits > > CVSNT 2.0.62.1817 seems to always create a new revision, even if the > file has not changed: > > C:\mytest\sandbox>cvs stat test.txt > =================================================================== > File: test.txt Status: Up-to-date > > C:\mytest\sandbox>touch test.txt > > C:\mytest\sandbox>cvs stat test.txt > =================================================================== > File: test.txt Status: Locally Modified > > C:\mytest\sandbox>cvs commit -m "No change" test.txt > Checking in test.txt; > /mytest/rep/sandbox/test.txt,v <-- test.txt > new revision: 1.9; previous revision: 1.8 > done > > C:\mytest\sandbox>cvs log test.txt > > RCS file: /mytest/rep/sandbox/test.txt,v > Working file: test.txt > head: 1.9 > branch: > locks: strict > access list: > symbolic names: > keyword substitution: kv > total revisions: 9; selected revisions: 9 > description: > ---------------------------- > revision 1.9 > date: 2005/03/31 19:57:15; author: tma; state: Exp; *lines: +0 -0*; > kopt: kv; commitid: 960424c561b0271; filename: t > est.txt; > No change > ---------------------------- > > -Torsten _____________________________________________________________________ This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this message is strictly prohibited. If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any copy or distribution. Thank you.