info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is there a limint on the number of branches in CVS?


From: Mark E. Hamilton
Subject: Re: Is there a limint on the number of branches in CVS?
Date: Wed, 17 May 2006 16:52:20 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.12) Gecko/20050920



Todd Denniston wrote:

Out of curiosity, has anyone tested what happens if the revision numbers
roll over?



I suspect all hell breaks loose.  :-)



I suspect you're right.


Would either of you have a better plan for testing the roll over than to do something like the following script? With _an_ unmodified CVS I believe it would take ~18.5 hours to get to 65534, to get to 2147483647 it would only take ~68 years by just checking in new revs. So we may have a little time left to fix the problem. :)

BTW, looks to me like we still did not have a problem at 4294967294 on a Linux system running on a Intel(R) Xeon(TM) CPU 1.50GHz.

Well, I just created a new repos, added three test files, then manually modified the ,v file, changing all instances of 1.1 to 1.65535 in one file, 1.2147483648 in the second file, and 1.4294967295 in the third. After updating in my working directory I changed and committed all of them twice. Looks to me like it didn't have any real heartburn.

(Did it in about 10 minutes, too, without a single (new) gray hair! ;) )

sahp6613% cvs commit -m 'Test 1'
cvs commit: Examining .
Checking in test1.dat;
/var/tmp/mhamilt/repos/test/test1.dat,v  <--  test1.dat
new revision: 1.65535; previous revision: 1.65534
done
Checking in test2.dat;
/var/tmp/mhamilt/repos/test/test2.dat,v  <--  test2.dat
new revision: 1.2147483648; previous revision: 1.2147483647
done

sahp6613% cat test1.dat > test2.dat ; cat test2.dat > test1.dat


sahp6613% cvs commit -m 'Test 2'
cvs commit: Examining .
Checking in test1.dat;
/var/tmp/mhamilt/repos/test/test1.dat,v  <--  test1.dat
new revision: 1.65536; previous revision: 1.65535
done
Checking in test2.dat;
/var/tmp/mhamilt/repos/test/test2.dat,v  <--  test2.dat
new revision: 1.2147483649; previous revision: 1.2147483648
done

sahp6613% cat test1.dat > test2.dat ; cat test2.dat > test1.dat

sahp6613% cvs commit -m 'Test 3'
cvs commit: Examining .
Checking in test1.dat;
/var/tmp/mhamilt/repos/test/test1.dat,v  <--  test1.dat
new revision: 1.65537; previous revision: 1.65536
done
Checking in test2.dat;
/var/tmp/mhamilt/repos/test/test2.dat,v  <--  test2.dat
new revision: 1.2147483650; previous revision: 1.2147483649
done

sahp6613% cat test1.dat >> test3.dat
sahp6613% cvs commit -m 'Test 4'
cvs commit: Examining .
Checking in test3.dat;
/var/tmp/mhamilt/repos/test/test3.dat,v  <--  test3.dat
new revision: 1.4294967295; previous revision: 1.4294967294
done

sahp6613% cat test1.dat >> test3.dat

sahp6613% cvs commit -m 'Test 5'
cvs commit: Examining .
Checking in test3.dat;
/var/tmp/mhamilt/repos/test/test3.dat,v  <--  test3.dat
new revision: 1.4294967296; previous revision: 1.4294967295
done



--
----------------
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666





reply via email to

[Prev in Thread] Current Thread [Next in Thread]