Anderson Lizardo wrote:
Alexander E. Patrakov wrote:
With fsfs, that's as easy as editing
/home/svn/repositories/LFS/db/revprops/6803 on belgarath. Don't forget
to change "V 160" to "V 161". BTW it looks like I have enough
permissions to do that :) Do you want me to fix the log or prefer doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander E. Patrakov wrote:
>
> With fsfs, that's as easy as editing
> /home/svn/repositories/LFS/db/revprops/6803 on belgarath. Don't forget
> to change "V 160" to "V 161". BTW it looks like I have enough
> permissions to do that :) Do you want me t
Alexander E. Patrakov wrote:
I suggest dumping and restoring. With my toy repository at
file:///home/patrakov/svn-test, the sequence of actions is:
I understand that with fsfs this sequence of actions may be suboptimal.
With fsfs, that's as easy as editing
/home/svn/repositories/LFS/db/r
Anderson Lizardo wrote:
I understand, but in this case "svn log --xml" should have output "ΓΌ" as
some strange character (maybe not even a valid UTF-8 sequence) and not
just keep it in "plain" ISO-8859-1 (which is what happens), right?
Almost correct. "svn log --xml" should output \xc3 \xbc in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander E. Patrakov wrote:
> Anderson Lizardo wrote:
>> FIY, the Subversion commit messages need always to be written either
>> in Unicode or plain ASCII, so "svn log --xml" can output valid XML
>> data. So please, setup your favorite editor to one o
Anderson Lizardo wrote:
Hi dev's,
FIY, the Subversion commit messages need always to be written either
in Unicode or plain ASCII, so "svn log --xml" can output valid XML
data. So please, setup your favorite editor to one of these encodings
before issuing a "svn commit".
A bit wrong. SVN us
