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

Re: [PATCH] enum svn_node_kind -> svn_node_kind_t

From: <cmpilato_at_collab.net>
Date: 2002-11-05 23:53:22 CET

=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:

> The funny thing is, though, that we can't add such an option. We have
> to pass the context parameter down the call chain first, and move the
> config file reading from the libraries into the client, because the
> client is the only bit that sees command-line options. Wheee...

Actually, I was thinking today that this is what we should do anyway.

Subversion could define an svn_config_opt_t structure (since
svn_config_t is already taken) that is attached to all relevant WC API
calls (and svn_client ones by extension). Then each client (cmdline
or otherwise) would populate this structure any way they see fit to do
so. Passing NULL for the structure argument would mean simple "no
special config".

Is this insane? Have we already gone here in discussion?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 5 23:56:10 2002

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.