From: Anthony Liguori <aliguori-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: ichiyanagi.yoshimi-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org
Subject: Using UTF-8 encodings for SVN commit message
Date: Wed, 24 Jan 2007 21:19:56 -0600 [thread overview]
Message-ID: <45B821DC.5020200@cs.utexas.edu> (raw)
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).
Thanks!
Regards,
Anthony Liguori
-------------------------------------------------------------------------
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
next reply other threads:[~2007-01-25 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 3:19 Anthony Liguori [this message]
[not found] ` <45B821DC.5020200-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
2007-01-25 4:19 ` Using UTF-8 encodings for SVN commit message Anthony Liguori
2007-01-25 7:13 ` Muli Ben-Yehuda
2007-01-25 7:47 ` Avi Kivity
[not found] ` <45B860A4.80000-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-26 14:49 ` Christopher Boumenot
2007-01-26 18:19 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45B821DC.5020200@cs.utexas.edu \
--to=aliguori-nzps4cjig2hvqtjrzfazuq@public.gmane.org \
--cc=ichiyanagi.yoshimi-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox