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.
Bo Berglund <bo.berglund at telia.com> writes: > > Just from the top of my head: > The contents of the RCS files is the realm of the *server* so I don't > think that a client can cause the RCS files to become corrupt unless > you are accessing the repository using :local: from the Tortoise > client. In that case there will be definite problems like these. > So what was your connection protocol? (Which connection string did you > use?). > We use "pserver". The normal CVS users don't even know where the archives are stored in the filesystem on the CVS server. And the archives are not even accessible via the filesystem from our Windows clients. So I'm quite sure that this has happened using the "pserver" protocol. Isn't it possible that the CVS client and server sometimes "trust" each other too much? Then a label produced in the client (CVSNT) of the form "SOME_LABEL:_H_" could be transferred over the CVS-pserver-protocol and the server would store it without even knowing that it stored a "strange" label. Am I right in suspecting that the "_H_" is some kind of extension introduced in CVSNT? If so, where can I find information about it? What does it mean? In my previous mail I wrote: > I have tried to ask the developer using TortoiseCVS what sequence of > operations he did, but I have not found out the exact circumstances > when the ":_H_:" is written to the server. We suspect it has to do > with merging to/from the branch. One thing I forgot to mention then, was the fact that the archives of the problematic files are in the "Attic" on the server since they were added on the branch (this is the case at least for the files I have looked at in detail). /Johan Holmberg