From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Christopher Boumenot <boumenot-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
aliguori-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org
Subject: Re: Using UTF-8 encodings for SVN commit message
Date: Fri, 26 Jan 2007 20:19:09 +0200 [thread overview]
Message-ID: <45BA461D.8070005@qumranet.com> (raw)
In-Reply-To: <epd4e3$lrj$3@sea.gmane.org>
Christopher Boumenot wrote:
> > I can do a dump/edit/load cycle if you like.
>
>
> Commit messages in SVN are not idempotent. If you have configured SVN
> to allow it, you can just re-edit the commit message.
>
> $ svn propedit svn:log --revprop -r <revision>
>
>
Thanks for the tip. I fixed the two instances of the error I could find.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-01-26 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 3:19 Using UTF-8 encodings for SVN commit message Anthony Liguori
[not found] ` <45B821DC.5020200-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
2007-01-25 4:19 ` 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 [this message]
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=45BA461D.8070005@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=aliguori-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org \
--cc=boumenot-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.