line endings redux

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Parks пишет:
> On Mar 5, 2007, at 8:18 PM, John Whitley wrote:
>> * Binary file detection/handling.  EOL conversion can corrupt files,
>> so care
>>   is needed here.
> 
> I want to point out an alternate way to implement this: files are
> committed as they are now, but are transformed when they're accessed in
> the repository. In other words, files are normalized on read, instead of
> write. This could be used for keywords (e.g. $Id$), too.
> 
> I imagine this would make annotation harder, but it is very safe. 

It's not only make annotation harder, but also checkout, cat and diff between revisions.
And harder means slower. From performance point of view I don't like to go this way.
(and keywords is only way to worse performance, IMO).

> This
> doesn't seem like it would require a working tree format bump, but I
> don't really understand bzr internals.

Format bump is needed because current format cannot be adopted to store EOL property.

> 
> Another way to get the same effect is to normalize line endings on
> commit and then record which line endings were changed.

I don't understand your last thought: "record which line endings were changed".
What you actually means? Why for to record anything about actual eol, if we keep eol property that
applied to all file content?

- --
Alexander

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF7dOSzYr338mxwCURAkqeAJsGYyTHMHR6ZRrShwAtqKgIVgb0UgCcD6Jg
nFBxpefXXXLFPuOqEbJ9CkQ=
=Tf7G
-----END PGP SIGNATURE-----