[Top][All Lists]

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

[Bug-cssc] [bug #57240] new error handling causes non-zero exit statuses

From: Greg A. Woods
Subject: [Bug-cssc] [bug #57240] new error handling causes non-zero exit statuses even for warnings
Date: Sat, 16 Nov 2019 14:44:44 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36

Follow-up Comment #1, bug #57240 (project cssc):

I suspect the difference might be in when or how the 'i' flag is enforced.

Heirloom SCCS gives a solid error when trying to extract a version which does
not have ID keywords, as does CSSC.

However CSSC seems to do so for any version.

The older version 1.4.0 was giving spurious (about 1-5% of runs) errors, but
for failing to unlink the file "-" (which "get -p" probably shouldn't have
created in the first place.

I really don't understand, and never did, why "get" enforces the 'i' flag. 
The flag can be added to a file after many non-conforming revisions are
already present, and from that point forward those old revisions are
irretrievable.  I can find no rational whatsoever anywhere for this behaviour,
and never could.


Reply to this item at:


  Message sent via Savannah

reply via email to

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