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.
The silence is deafening. :-) Does this mean "ya, we know. Who cares?"...? WinCVS does it somehow for "cvs commit -m "foo\n foo"" right? Here is an example: I check in three files and in the WinCVS comment box, I type: -------------------------------------------8<-------------------------- Changing the policy on branching. Using tags instead. unless a branch is the only solution. I refer to a doc about branching that is not checked in yet. I'll work on that next. -------------------------------------------8<-------------------------- I push OK, and this comes out in the WinCVS "shell": -------------------------------------------8<-------------------------- cvs commit -m "Changing the policy on branching.\nUsing tags instead.\nunless a branch is the onl..." IGT_Development_Process_under_CVS.html tagdialog.gif tagxButton.gif (in directory D:\ProjectWeb\CvsProject\) Notice: commitinfo: ok Notice: verifymsg: ok. Checking in IGT_Development_Process_under_CVS.html; /repo1/WebServer/ProjectWeb/CvsProject/IGT_Development_Process_under_CVS.htm l,v <-- IGT_Development_Process_under_CVS.html new revision: 1.24; previous revision: 1.23 done ... etc ... ------------------------------------------8<---------------------------- It MUST be lying about the command line, right? It shows my comment which I purposely made really long is *truncated* with a "..." however, the entire comment makes it into the log with the newlines intact! Here is the log: ------------------------------------------8<---------------------------- ---------------------------- Revision : 1.24 Date : 2003/9/2 23:18:22 Author : 'reed' State : 'Exp' Lines : +766 -761 Keyword : 'kv' CommitID : 'e583e55253c0000' Description : Changing the policy on branching. Using tags instead. unless a branch is the only solution. I refer to a doc about branching that is not checked in yet. I'll work on that next. ---------------------------- ------------------------------------------8<---------------------------- So, it has got to be do-able. right? right? :-) Thanks, __________________________________ Reed Lawson IGT Firmware Engineering (775) 448-0755 > -----Original Message----- > From: Lawson.Reed > Sent: Friday, August 29, 2003 1:06 PM > To: 'cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook' > Subject: [cvsnt] embedding newlines in the -m option. how? > > > Hi. > > I'm trying to write a script to alter the comment in a > revision of a file using "cvs rcs -m<rev>:"comment" file.c" > but I need to support multiple lines. How do you > properly embed newlines in the -m option? > > I tried everything I know, and I can not seem to > find a successful way to do it. They keep coming out in > the log looking like this: > > "It is challenging trying to get multi-line\\ncomments > working from a script > and the -m option\\nI can not figure out how to do it." > > Any ideas? > > $ cvs version > Client: Concurrent Versions System (CVSNT) 2.0.2 (client/server) > Server: Concurrent Versions System (CVSNT) 2.0.5 (client/server) > > Thanks, > > __________________________________ > Reed Lawson > IGT Firmware Engineering > (775) 448-0755 > > _______________________________________________ > 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 >