[cvsnt] Problem branching, then error on commit in CVSNT
andrew at cushen.com
Thu May 8 03:19:33 BST 2008
The e-mail seems to have come across just fine.
I've gotten to this point OK:
> Now modify each one (just add a comment or blank line) and commit a change
back to the branch:
Ugh. There are *hundreds* of files to modify! I don't suppose I could get
away with just modifying the bad files?
No? I didn't think so. Oh well... ;-)
BTW, could you tell what the condition of the trunk, and/or the Tagged
revisions, was? Are they messed up as well?
If I have to settle for just having the Release branch we've been working on
fixed, that's OK. But I'd like to know if I can safely check out any of the
other code, or if I should just work from the Release branch (and any new
branches I may create from it).
I'll let you know the results of the check-in when I finish modifying the
More information about the cvsnt