Martin v. Löwis wrote:
> It complains that, in revision 36760, there was no release24-main
> directory, so it can't know what the history is. I would consider it
> a bug: it could know that release24-maint was a copy of trunk
> which was made after 36760, so it could conclude I meant to
> perform t
[EMAIL PROTECTED] wrote:
> Okay, I got it. I was asking for that revision on the release24-maint
> branch, but it was actually applied to the trunk. It shows up now in the
> maintenance branch, but still has to be queried for on the trunk.
My subversion (1.2.3) gives me a slightly more legible o
>> svn log --verbose -r 36760
>>
>> When I run it I get this error:
>>
>> svn: REPORT request failed on
'/projects/!svn/bc/36760/python/branches/release24-maint'
>> svn: '/projects/!svn/bc/36760/python/branches/release24-maint' path not
found
Tim> I'm not sure, and
[EMAIL PROTECTED]
...
> Wanting to investigate that further, I checked the developer's FAQ and found
> this command to view the checkin history for that rev:
>
>svn log --verbose -r 36760
>
> When I run it I get this error:
>
>svn: REPORT request failed on
> '/projects/!svn/bc/36760/python
I'm investigating some problems we're having at work with SIGUSR1 handling.
Our apps tend to see KeyboardInterrupt when sent SIGUSR1 signals. We're
still running 2.3.4 but are in the process of installing/testing 2.4.2.
A couple "find ... | xargs egrep -i usr1" commands in the 2.3 and 2.4 trees
s
