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 email@example.com.
Hello, We have experienced the same problem somme time ago. I found a kind of work-around: 1- commit the unicode file on the HEAD, 2- merge the HEAD into the branch, 3- commit the file on the branch. Notes that we didn't try to delete the file on the HEAD after step 3- with the admin "-o" command (because in ours case we need the same file on the two branchs) so I don't know if it breaks something or not (let me know if you are succesfull with this). Regards, Nicolas. > -----Message d'origine----- > De : cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]De la part > de Klaus Beyer > Envoye : lundi 9 juillet 2007 08:46 > A : cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Objet : [cvsnt] Unicode file line end defect on branch. > > > I discovered the following problem: > > 1) branch a Unicode file > 2) modify the file on the branch. > 3) commit the file > > The result is: all lines gets an extra CR. > This happens always on the 1. branch. On the main trunk it's OK and on > the 2. branch it's OK again. > I use version 2.5.03 Build 2382. I tried Build 2704 and I got the same > result. > > Is this a known issue? What can I do to avoid this? > > > Thanks, > Klaus > > > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >