On Jan 7, 2008 5:12 PM, Klaus Metzger <[EMAIL PROTECTED]> wrote: > Hello James, > > enclosed answers to your question 1 to 4 and 6,7 and the additional from > your next email > > A. The command > >get -l SCCS/s.P26J000001.input > delivers the l.P26J000001.input > > B. The command > >get -l SCCS/s.P26J000001.input
As far as I can determine, this command is identical to the previous one, is that what you planned? Or did you mean "-lp"? > which Im mostly using, does not create the l file, it just prints the > result on the screen > > storm_KPM> get -lp SCCS/s.P26J000001.input > the message on the screen is > then-------------------------------------------- > 1.7 > 1.7 08/01/07 07:58:35 butch > comment with two tabs > > 1.6 08/01/07 07:58:16 butch > comment with one tab > > 1.5 08/01/07 07:56:28 butch > abcde > > 1.4 08/01/07 07:54:38 butch > dsjkhfkjhdsfjhdshfjhdfkjhdshfadshf d > > 1.3 03/11/06 14:57:21 mueller > > 1.2 03/11/06 14:56:49 mueller > > 1.1 03/11/06 14:56:16 mueller > date and time created 03/11/06 14:56:16 by mueller > > 13 lines > end of screen-------------------------------------------------------- > > In that case the version V1.1 to 1.3 were stored without any comment > > Your questions. > 1. To simulate an I/O error on the l file I set it to unread- and unwritable > (# chmod 000 l.P26J000001.input) > Then issued the command > > storm_KPM> get -l SCCS/s.P26J000001.input > the message on the screen is------------- > 1.3 > 13 lines > end osf message---------------------------- > > It seems that there is no proper handling of that error wrt the l-file. > The g-file (in this case P26J000001.input) is still created properly > > 2. The mode of the l-file is > storm_KPM> ls -l P26J000001.input > -r--r--r-- 1 butch 25 904 Jan 7 07:51 P26J000001.input > > 3. It is not possible to insert multiple lines as comments so there is > no need to handle it. Multi-line comments can be added either by using a backslash interactively, or by using delta -y "multi line comment" > 4. Leading tabs see example B. above I think your file has become corrupted; even the tabs that should be there seem to be missing. > 5. I have to investigate, I will come up later > > 6a. Your question :Another question: if more than one file is gotten, > what does "get -L" > do? Does the format change? > > > storm_KPM> get -p -L SCCS/s.P26J000001.input > 6b. get -L -p SCCS/s.P26J000001.input : no difference to 6a > > 7. Im not quite sure if I understand the questions. Why should be the > l-file a > broken symbolic link. It is created by the command as a file and not as a > link. ln -s l.foo thisfiledoesnotexist get -lp s.foo Here l.foo starts off as a broken link. The question is, does l.foo get deleted and recreated, or is the symlink followed, creating thisfiledoesnotexist? > 8. more files: > storm_KPM> get -L SCCS/s.P26J000001.input SCCS/s.P26J000000.input [...] > hence, it displays both outputs one after another > please note that there are no comments in the second file > > The format does not change > > > I hope I met your questions Thanks; as far as I can tell, the existing CSSC implementation works in the same way. > Enclosed > - the man pages from the get command (just in case I didn't send it alread) I have read the manual pages; they are available on-line, for example. But they are not useful for making documentation for CSSC, as the copyright in those files belongs to HP (I assume), not to the FSF or you. But thanks anyway. James. _______________________________________________ cssc-users mailing list cssc-users@gnu.org http://lists.gnu.org/mailman/listinfo/cssc-users
