Re: Using UTF-8 encodings for SVN commit message

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Anthony Liguori wrote:
> Howdy,
>
> I have a bit of an odd request.  I've been using tailor to mirror KVM 
> in mercurial which is my preferred SCM.  This has worked quite well up 
> until sometime in December when tailor started throwing errors.
>
> I finally got around to looking into it and discovered the source of 
> the problem.  It seems that on December 26th, Avi committed a patch 
> from Yoshimi Ichiyanagi "kvm: initialize kvm_arch_ops in kvm_init()".
>
> The problem is that the commit message (which was likely copy-pasted 
> from an email) contains a character that is neither ASCII nor is it 
> UTF-8.  SVN commit messages should be encoded in UTF-8.  The reason 
> for this is that SVN allows exporting information about the repository 
> in XML which is marked as UTF-8 encoded.
>
> If commit messages aren't valid UTF-8, SVN generates invalid XML.  
> While SVN should probably generate an error when committing non-UTF8 
> messages, we shouldn't be doing it in the first place.
>
> Is there any way to fix this?  I'm going to try to find a way to hack 
> around it in tailor but I suspect this will break other SVN tools too.
>
> If nothing else, I was hoping we could be a bit more careful about 
> this in the future (if that's at all possible).

I can do a dump/edit/load cycle if you like.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV