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

Re: Third-party provider funcs in our API: did we expose too much?

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 26 Jul 2012 22:20:28 +0200

On Thu, Jul 26, 2012 at 04:12:41PM -0400, C. Michael Pilato wrote:
> Can anyone explain to me why the following symbols are exposed in the public
> Subversion API?
> svn_auth_get_platform_specific_provider
> svn_auth_get_windows_simple_provider
> svn_auth_get_windows_ssl_client_cert_pw_provider
> svn_auth_get_windows_ssl_server_trust_provider
> svn_auth_get_keychain_simple_provider
> svn_auth_get_keychain_ssl_client_cert_pw_provider
> svn_auth_get_gnome_keyring_simple_provider
> svn_auth_get_gnome_keyring_ssl_client_cert_pw_provider
> svn_auth_get_kwallet_simple_provider
> svn_auth_get_kwallet_ssl_client_cert_pw_provider
> svn_auth_get_gpg_agent_simple_provider
> svn_auth_gnome_keyring_version
> svn_auth_kwallet_version

I would guess it's a simple case of gratuitous copy-pasting,
as in the first provider was made public and the others blindly
followed the same pattern.
Received on 2012-07-26 22:21:08 CEST

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

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