On Thu, Feb 9, 2012 at 6:53 PM, Greg Stein wrote:
The S:txdelta element was not requested by the client, so it freaks
> out when it sees the unknown element.
>
Makes sense, we just deployed an update that fixes that and a few other
bits that turned up while testing with ra_serf.
The chunked req
On Wed, Feb 8, 2012 at 12:59 PM, Greg Stein wrote:
So... this isn't really so much about "svn must allow for HTTP/1.0"
> (yes, we'll work on it), but that github could also provide better
> service overall by updating its proxy.
>
I've been looking into what it would take to update our proxy. I
x27;re not returning the new custom headers, so I'd expected that ra_serf
would fall back.
Do you know whether there's something else that the "SVNAdvertiseV2Protocol
off" config directive does to OPTIONS or other responses?
On Wed, Feb 8, 2012 at 1:47 PM, Daniel Shahaf wrote
That pointed me in the right direction, thanks.
It was a bug related to tag versions, and we just deployed a fix. I was
able to do a checkout with a 1.7 client, let me know if you have any
problems.
On Wed, Feb 8, 2012 at 12:41 PM, C. Michael Pilato wrote:
> The GitHub server is definitely tryi
Thanks for checking - we want to be fully compatible so any information
like this helps.
The checkout URL is the same as the HTTP clone URL, and the .git suffix is
optional for both git and svn clients.
I may have misunderstood what's up with the ra_serf library, I thought that
was related to HTT
C. Michael Pilato collab.net> writes:
>
> Well, supported by whom?
>
> At first blush, it would appear that the GitHub server didn't transmit a
> valid svn:entry:committed-rev property value for one of the directories your
> checkout is attempting to register with Subversion's working copy
> a
6 matches
Mail list logo
