Re: editors get lost with running an update

Using the diff command is no option, because it uses E responses instead of sending the file content. This causes major troubles with non-ASCII-characters. -- Best regards, Thomas Singer _ smartcvs.com Jim.Hyslop schrieb: Thomas Singer wrote: We've encountered a problem with GNU CVS 1

Re: editors get lost with running an update

Using the diff command is no option, because it uses E responses instead of sending the file content. This causes major troubles with non-ASCII-characters. -- Best regards, Thomas Singer _ smartcvs.com Jim.Hyslop schrieb: Thomas Singer wrote: We've encountered a problem with GNU CVS 1.1

RE: editors get lost with running an update

Thomas Singer wrote: > We've encountered a problem with GNU CVS 1.12.9. Please see > the following log. [...] > CVSNT 2.0.58d behaves correctly, it keeps the editors information. > > What request SmartCVS should send, so GNU CVS 1.12.9 just > sends the original > content of the file without des

editors get lost with running an update

Hi, We've encountered a problem with GNU CVS 1.12.9. Please see the following log. First, we check out a simple module "test" (cvs watch on was called before): [EMAIL PROTECTED]:~/test$ la total 8 drwxr-xr-x2 tom tom 4096 Feb 27 13:34 . drwxr-xr-x 34 tom tom 4096 F