-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Munn wrote:
> So doing an SVK mirror of the repository should work now, barring
> any further surprises. I'm starting the SVK sync now; we'll see what
> happens.
Confirmed; the SVK mirror took about 18 hours, but it complete
-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:
>
>
>
-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-mes
-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 tha
ning the following:
echo "New commit message goes here" > new-message.txt
svnadmin setlog --bypass-hooks -r 4077 /path/to/repos new-message.txt
If there are other, similar problems later in the SVN repository, I was
unable to find them because the SVK mirror process consistently halt
using EXPR as VAR:
~BLOCK
Reads similarly to "with", but leaves the "with" keyword open for
possible use later.
Since it seems traditional for one to introduce oneself upon first
posting to python-dev, my name is Robin Munn. Yes, my name is just one
letter different from R
