[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN/Python/Shared Library/sccs2svn help please!

From: Joey Mukherjee <joey_at_swri.edu>
Date: 2005-03-18 17:17:25 CET

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)
>
> You're behind a web proxy. Classic error message of a proxy that
> blocks webdav requests like REPORT.

Ok, so my company is blocking something useful. That's normal.
However, is there something else I can do to get a tarball of the
changes? Even a list of filenames would be helpful. There is no
timetable for when 1.1.4 is going to be released, is there?

>> I tried getting on the website (http://svn.collab.net) to maybe see
>> what files had changed, and this seems to be impossible. It would be
>> nice if there was something I could click on and see a list of all
>> the files that between that revision and another. Is that possible?
>
> Sure, viewcvs is running on svn.collab.net. Enjoy.

This doesn't help actually. Unless you go to every file, there seems
to be no way to click on something that "show me all the changes that
are on this branch from the trunk". I would love to be proven wrong
however.

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 17:25:07 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.