On Mar 18, 2005, at 10:28 AM, Ben Collins-Sussman wrote:
> On Mar 18, 2005, at 10:17 AM, Joey Mukherjee wrote:
>>
>> On Mar 17, 2005, at 8:32 PM, Ben Collins-Sussman wrote:
>>
>>> Probably your best option would be to grab the patch adding support
>>> for Swig 1.3.24, which is planned for inclusion in Subversion 1.1.4:
>>>>>
>>>>> $ svn diff http://svn.collab.net/repos/svn/branches/1.1.x-new-swig
>>>>> -r13071:HEAD
>>>>
>>>> I tried this command and I get the following:
>>>>
>>>> svn: REPORT request failed on
>>>> '/repos/svn/!svn/bc/13457/branches/1.1.x-new-swig'svn: REPORT of
>>>> '/repos/svn/!svn/bc/13457/branches/1.1.x-new-swig': 400 Bad Request
>>>> (http://svn.collab.net)
>>>>
>
> Try using https://. Most proxies can't block requests over SSL.
{joey}[elmer:~/subversion-1.1.3]31: svn diff
https://svn.collab.net/repos/svn/branches/1.1.x-new-swig -r13071:HEAD
svn: Unrecognized URL scheme
'https://svn.collab.net/repos/svn/branches/1.1.x-new-swig'
Should svn be able to use https as a transport mechanism?
Joey
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 18 20:03:29 2005