line endings redux

[Alexander Belchenko]

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

Nicholas Allen пишет:
>> There was some (relatively) recent discussion here along those lines
>> (Jan 16,17,31 and Feb 1st).  For convenience, I'll summarize the last
>> state of the discussion as I read it here:
>>
>> * A .bzrignore-like file (proposed: .bzreol) with globs stores the
>> defaults
>>   for line ending conventions.
> I think it would be better if it were more general than this. That is,
> line endings are just a versioned property on a file and so a file that
> decides on default properties for newly added files that match reg exps
> would be better IMHO.  Then you can add whatever properties you want
> into this file...

Per example?
I think we don't need to open box with worms and put the arm to the user. The set of properties
should be as small as possible, because of performance.
Right now I think we definitely need:
1) eol type for text files, and explicit mark binary file explicitly
2) encoding of text contents

Because of performance I think that bzr don't need support of CVS-style keywords ($Id: $).

> Also another thing that would be nice is a file encoding property too.
> The file would be stored in the repository using one encoding but could
> be different encoding in the working tree. I'm not sure how bzr deals
> with this issue at the moment....

It's essential for me.
I think in repository text files should be stored in utf-8.

- --
Alexander

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

iD8DBQFF7dObzYr338mxwCURAjFyAJ4/iZviSZtFMlDhR5h9arhov0eOkgCfSuCn
nukLwK5iXp3K5o46MdaQ85A=
=5VjI
-----END PGP SIGNATURE-----