[cvsnt-commits] Cvs Commit: cvsnt

arthur.barrett at march-hare.com arthur.barrett at march-hare.com
Thu Nov 8 23:30:09 GMT 2007


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.


CVSROOT:	/usr/local/cvs
Module name:	cvsnt
Changes by:	arthur.barrett at march-hare.com		Thu Nov  8 23:29:27 2007
On host:	mail.march-hare.com

Directory: cvsnt/cvsio

M CvsEntry.cpp		1.24 -> 1.25	Bug Id: 
M RecurseRepository.cpp		1.20 -> 1.21	Bug Id: 

Directory: cvsnt/src

M add.cpp		1.72 -> 1.73	Bug Id: 
M checkout.cpp		1.78 -> 1.79	Bug Id: 
M client.cpp		1.181 -> 1.182	Bug Id: 
M CompatRecursion.cpp		1.72 -> 1.73	Bug Id: 
M server.cpp		1.215 -> 1.216	Bug Id: 
M update.cpp		1.148 -> 1.149	Bug Id: 

Log message:
This resolves a bug where a file is added on a directory and
a sub-directory where neither is the module, eg:
cvsnt/installer/xx.wxs
cvsnt/installer/binary/xx.gif

if you commit from "within" cvsnt/installer then what previously
would happen is that xx.gif would get added but xx.wxs would not
because the directory "." on the server would not contain a
valid CVS/Repository file.

This change now means that CVS/Repository should be correct in
tmp.

I've also added a "close" to "ent" when all these "dummy"
directories get created, which appears to improve the ACL 
checking on "parent" dirs, which is probably more important now 
that it was previously

According to testcvs.bat/testcvs.py I havn't broken anything that
wasn't already broken...

More reams of debugging added.  Watch out for things I added 
with a debuglevel of "10" if these are enabled then it gets in the
way of the protocol and causes everything to fail, but they do
add a lot of help to the servertracefile (which gets all msgs).





More information about the cvsnt-commits mailing list