[MERGE][#295161] Ensure valid messages and revision properties

[John Arbash Meinel]

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

At the moment, we have a small issue with how we (de)serialize commit
messages and revision properties because we go through XML.
Specifically, when writing, we are allowed to write things like "\r" and
"\r\n" to the string, but when those strings get read back, they will
all be normalized to "\n". (This happens as part of the Expat parsing.)

This patch helps prevent those sorts of things being written to the
repository, by checking the strings at commit time. I have an associated
patch for bzr-gtk which sanitizes the messages before they get committed.

It is also designed that this can be configured by the Repository, in
case future formats can support more characters.

This is a first step towards proper handling of bug #295161.
Specifically, this is a bzr fix to force clients to do the right thing,
and I'll post a couple patches to bzr-gtk to be a good client.

John
=:->


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

iEYEARECAAYFAkkbwsYACgkQJdeBCYSNAAOAnACdGiyxZq2iXf3jUcd+QZkInz2f
4Q0AmwWLFzPk7UvTfG6mlswzg957o2k+
=rgG2
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: revision_strictness.patch
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20081113/4e70e8ee/attachment-0001.diff