-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
Robin Munn wrote:
Revision 4077 is fine now. However, the same problem exists in revision
4284, which has a 0x01 character before the word add. Same solution:
I now have fixed that as well.
Regards,
Martin
And my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to mirror the brand-new Python SVN repository with SVK, to
better be able to track both the trunk and the various branches. Since
I'm not a Python developer and don't have svn+ssh access, I'm doing so
over http. The process fails when
Robin Munn wrote:
echo New commit message goes here new-message.txt
svnadmin setlog --bypass-hooks -r 4077 /path/to/repos new-message.txt
Thanks for pointing that out, and for giving those instructions.
I now corrected the log message.
Regards,
Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
Robin Munn wrote:
echo New commit message goes here new-message.txt
svnadmin setlog --bypass-hooks -r 4077 /path/to/repos new-message.txt
Thanks for pointing that out, and for giving those instructions.
I now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Munn wrote:
Revision 4077 is fine now. However, the same problem exists in revision
4284, which has a 0x01 character before the word add. Same solution:
echo New commit message goes here new-message.txt
svnadmin setlog --bypass-hooks -r
Robin Munn wrote:
Revision 4077 is fine now. However, the same problem exists in revision
4284, which has a 0x01 character before the word add. Same solution:
I now have fixed that as well.
Regards,
Martin
___
Python-Dev mailing list
