[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Large file actual performance report; cvs use of ,v header issometim
From: |
Arthur Barrett |
Subject: |
RE: Large file actual performance report; cvs use of ,v header issometimes non-optimal. |
Date: |
Fri, 18 Jan 2008 13:38:29 +1100 |
Todd,
> 'is 1.25 still the head/does it still exist?' on commit
> before working on
> anything else, because it always checks to see if you need to
> do an update
> before commit. Is this already the case in newer CVS's?
> And before someone says 'but he messed up the repo', which I
> agree... it
> should be trivial while checking 'if [current repo HEAD rev >
> current Entries
> rev]' also check 'if [current repo HEAD rev < current Entries
> rev]; {throw
> error/check to see if Entries rev still exists}'... at least
> for someone who
> knows where the first test is taking place now in the code.
> [Arthur, if you look this up in CVSNT, please drop a note to
> what file it is
> in for CVSNT, and the 10 lines around it... If I have to make
> a patch that
> would maybe help me find it in CVS.]
I try very hard to avoid looking in rcs.cpp since it tends to give me a
headache ;)
Regards,
Arthur