According to the apidoc, the `update_target' argument to svn_ra_do_update() can only contain a single path component. However, the backends all support multi path components to some degree: * ra_dav truncates the path and uses the last component (so, branches/1.4.x becomes 1.4.x) * ra_svn and ra_local support multi component paths It would be nice to have consistency across backends here, so I would propose (after a discussion with maxb on IRC) that a check be added to libsvn_ra that checks whether update_target is a single-component path and returns an appropriate error if it isn't. This will however, break existing 3rd-party apps that rely on the existing behaviour. Is that a problem?
Original issue reported by jrvernooij