[MERGE] line-endings support: part 1 of 2: versioned properties

[Robert Collins]

bb:abstain

I don't have to review this at the moment sorry. 

To whomever has time to review it, things to look out for based on our
lessons learnt with .bzrignore:

 - Unless this degrades cleanly in all cases this needs a new repo
format, and to not all pulling into old formats.
 - the disk format for this will be locked in place foreever if it uses
a 'userspace file', I had understood us to be wanting to avoid that
because of the upgrade headaches it gave us. We'll want to be able to
upgrade this capability too in a graceful manner. (E.g. the storage of
properties needs to be versioned if it is separate from the current
stored history formats).
 - if eol support is a core feature (I think it is) we should be using a
clear api to work with it, not something that permits arbitrary data to
be entered which we would not know how to handle. (e.g. if we use
versioned properties to store the rules for eol support, then there
needs to be an internal and external set, where plugins and users can
only directly alter the external set). This avoids many failure modes.

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080415/8df93870/attachment.pgp