[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-cssc] Test delta/errorcase.sh -> E30 .. E32

From: Joerg Schilling
Subject: Re: [Bug-cssc] Test delta/errorcase.sh -> E30 .. E32
Date: Fri, 20 May 2011 19:13:26 +0200
User-agent: nail 11.22 3/20/05

address@hidden (Joerg Schilling) wrote:

> Hi,
> why do you expect that it makes sense that a file with 
> no new line at the end should be "delta"d wihout error?
> Why do you expect that it is possible to retrieve back such
> a file and successfully compare it with the original file that
> misses the newline at the end?

I just found that you seem to assume that 

        admin -b -n s.foo

will create an amty history file suitable for encoded files.

It seems that the binary encoding flag has been introduced by Sun somewhere in 
the 1980s (it is supported on SunOS-4.1). On SunOS-4.1, you however will get an
error message:

/usr/sccs/admin -n -b s.foo
ERROR: 'b' keyletter can only be used with 'i' keyletter (ad33)

sccs help ad33

"'b' keyletter can only be used with 'i' keyletter"
The -b option, which indicates that a
file should be treated as binary and
checked in in an encoded form, may only
be specified if an SCCS file is being

SCCS on Solaris automatically assumes -n if you specify -i and it seems that 
the warning above has been removed for unknown reason, but the encoding flag 
is only added in case that you use -i.

We should discuss which behavior should be expected here......


 EMail:address@hidden (home) Jörg Schilling D-13353 Berlin
       address@hidden                (uni)  
       address@hidden (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

reply via email to

[Prev in Thread] Current Thread [Next in Thread]