I like to discuss a format that is intentionally incompatible to existing
implementations that use the SCCS-4.0 file format (that this way could require
a global project lock for implementations thatunderstand the followup format)
and I like to discuss a format that contains the enhanced information in a way
that will survive modifications made by SCCS-4.0 only aware implementations.
contains some thoughts from a time before I got the idea of using your method
of using '^Acmethod' to hide enhanced information as degenerated delta comment.
For this reason it still mentions that the converter program will cause a loss
> > At the time the test was written, I had not seen any version of SCCS
> > which supported binary files and actually turned on encoding for this
> > case.
> I believe that binary support a la uuencode was something that Sun did
> but I might be wrong.
As this is in SCCS from SunOS-4.0 and as it is not in SunOS-3.5, I would guess
that it has been introduced with NSE which has been demonstrated to us at
H.Berthold AG aprox. half a year before SunOS-4.0 came out for testing.
> > I'm pretty sure I was simply following the version of SunOS I was then
> > mostly testing against. Most of the early functional testing of CSSC
> > was done either by comparison with SunOS 4.1.x by myself
> Ahh, SunOS 4.1.1 had a lot of my efforts in it. I loved that release.
> Got a full set of manuals in my garage if anyone wants them.
well paper.... I would be interested in in files (I am not sure whether I can
still read 1/4 m^3 of QIC tapes), of course SCCS histories from SunOS-4.x would
be nice too ;-)