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

Re: start-commit hook client capabilities - mergeinfo only?

From: Branko ─îibej <brane_at_apache.org>
Date: Tue, 15 Sep 2015 05:38:33 +0200

On 15.09.2015 00:38, Brett Randall wrote:
> I have these versions:
> Client: svn, version 1.8.8 (r1568071) with ra_svn, ra_local and ra_serf
> Server: version 1.8.9 (r1591380) with fs_fs
> Using protocol https://
> I created and installed a start-commit hook that echos its third
> parameter (client capabilities) to a log file, ran a test-commit with
> the above software, and all that is echoed for client-capabilities is:
> mergeinfo. The repository access is over https:// .

I can confirm this happens with file:// and svn://, too.

> Any idea what is going-on here?

It could be we're confusing repository capabilities vs. client
capabilities somewhere in the code. In any case, the documentation (and
the implementation) clearly states we should be seeing client
capabilities here, so it looks like a bug at first glance.

> There are other capabilities
> mentioned in the documentation, such as "depth", "log-revprops", but
> these don't appear. In particular I am interested in the new
> auto-props feature in 1.8+ clients - is there a capability sent for
> that, and if not, should there be?

That would be the "inherited-props" capability. How these inherited
properties are interpreted (e.g., as in the case of svn:auto-props) is a
client-side decision; the server isn't consulted. A custom-built client
might announce the inherited-props capability but not actually interpret
auto-props, for example.

-- Brane
Received on 2015-09-15 05:38:40 CEST

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.