more performance work?

John Whitley whitley at bangpath.org
Wed Nov 7 21:44:03 GMT 2007


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

Robert Collins wrote:
> Well, for line endings, I think its a disastrous idea to store  
> differing
> versions commit after commit - very much not advisory. History size  
> will
> grow ridiculously, and diff will not DTRT if it is advisory.

YES.  The whole point of explicit line endings support is to  
effectively normalize what's stored by the VCS the the first place,  
so that diffs/merges never get horked because someone worked on an  
editor/platform that was using a different convention than previous  
code (or that was outright broken and mixed/changed line endings).

Regarding format bumps, I agree with Robert on this point as well.   
Line endings support as an optional plugin based on solely custom  
properties is useless, because it cannot guard the source against  
"line ending attacks" that impact diff/merge correctness.

However, another tack would be to include support for branch and/or  
repository level 'feature requirements' as a complement to custom  
properties.  This requires one format bump, after which Bazaar will  
refuse to operate on any branch/repo which requires a 'feature' that  
isn't provided by the core or an installed plugin.

This would allow plugins to provide orthogonal functionality,  
possibly utilizing data encoded in custom properties, where Bazaar's  
operation without that plugin can be incorrect.

Whether such a mechanism provides truly useful flexibility is an open  
question...

- -- John



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHMjGjr52Mexd941IRAjwaAKC+t3goSCKuZWLlyj5NJP2Q2ziDvACcC6Nm
DxCo4IqR+Ew5ciwYadnp+2Q=
=bleB
-----END PGP SIGNATURE-----



More information about the bazaar mailing list