home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.misc
- Path: sparky!uunet!mcsun!sunic!ericom!eos.ericsson.se!etxmesa
- From: etxmesa@eos.ericsson.se (Michael Salmon)
- Subject: Re: SCCS and binary files
- Message-ID: <1992Dec16.082518.4578@ericsson.se>
- Keywords: SCCS
- Sender: news@ericsson.se
- Nntp-Posting-Host: eos6c02.ericsson.se
- Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
- Organization: Ericsson Telecom AB
- References: <BzC2EG.Bq1@me.utoronto.ca>
- Distribution: comp
- Date: Wed, 16 Dec 1992 08:25:18 GMT
- Lines: 35
-
- In article <BzC2EG.Bq1@me.utoronto.ca>
- mitu@me.utoronto.ca (Adrian Mitu) writes:
- |>
- |>
- |> Can SCCS handle binary delta versioning? If not can someone reccomend
- |> a version-control system that does? I am reffering to storing binary
- |> files and their versions in a space-effificent manner (no un-necessary
- |> duplication of data).
-
- man 5 sccsfile gives:
-
- ^Af e 0|1
- The e flag indicates whether a source file is encoded
- or not. A 1 indicates that the file is encoded.
- Source files need to be encoded when they contain con-
- trol characters, or when they do not end with a NEW-
- LINE. The e flag allows files that contain binary data
- to be checked in.
-
- That is files containing that have other than printable and whitespace
- characters or are missing a terminating newline are encoded (I believe
- uuencoded). That also implies that insertion or deletion of binary data
- will result in all common data after the change being included in both
- deltas (presuming no complementary change).
-
- --
-
- Michael Salmon
-
- #include <standard.disclaimer>
- #include <witty.saying>
- #include <fancy.pseudo.graphics>
-
- Ericsson Telecom AB
- Stockholm
-