[Guido van Rossum]
Is there a way to prevent this kind of thing in the future, e.g. by
removing or rejecting change log messages with characters that are
considered invalid in XML?
Suppose TOP is the top of the Subversion repository. The easiest way is
providing a TOP/hook/pre-commit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Munn wrote:
So doing an SVK mirror of the repository should work now, barring
any further surprises. I'm starting the SVK sync now; we'll see what
happens.
Confirmed; the SVK mirror took about 18 hours, but it completed
successfully with no
I have a question after this exhilarating exchange.
Is there a way to prevent this kind of thing in the future, e.g. by
removing or rejecting change log messages with characters that are
considered invalid in XML?
(Or should perhaps the fix be to suppress or quote these characters
somehow in
Guido van Rossum wrote:
I have a question after this exhilarating exchange.
Is there a way to prevent this kind of thing in the future, e.g. by
removing or rejecting change log messages with characters that are
considered invalid in XML?
I don't think it can happen again. Without testing, I
