On 01/11/2013 02:23 PM, C. Michael Pilato wrote:
> Actually, I think I'll take a slightly differently approach here. Rather
> than have the client hit the "me resource" (which represents the whole
> repository), I'll have it hit the revision resource associated with the
> single revision that's be
On 01/11/2013 12:15 PM, C. Michael Pilato wrote:
> So. Looks like I'll be taking a little detour here to try to fix this in a
> compatibility-preserving way. Here's my plan:
>
> Server-side: Recognize which resource was hit with the request, looking for
> the (optional) path filter in the REPOR
While trying to minimize our 1.8 issue count, I found myself looking issues
#4287 (http://subversion.tigris.org/issues/show_bug.cgi?id=4287) and #4100
(http://subversion.tigris.org/issues/show_bug.cgi?id=4100). Both of these
involve problems using svnrdump to dump a revision range of a URL which n
3 matches
Mail list logo
