You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Eric Dorland <er...@mail.mcgill.ca> on 2003/04/05 03:36:32 UTC
Changes to exported symbols
I was thinking about how to implement text-base compression now that
compressed streams have been accepted. Looking at the way the config
system (since of course I want to make it configurable), I would need
to add arguments to svn_wc_get_update_editor and its kin to say
whether compression is desired or not. Since this are public
functions, this would be an API change. Is the API frozen at this
point?
If so, is there another way I can get the configuration information
into these functions? I must admit I find the config functions are I
bit inconvenient to get config info in these deeply nested
functions... am I missing something?
--
Eric Dorland <er...@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+
G e h! r- y+
------END GEEK CODE BLOCK------
Re: Changes to exported symbols
Posted by Eric Dorland <er...@mail.mcgill.ca>.
Excellent, since I already started working on it over the weekend :-D
Should have a patch later this week.
* Ben Collins-Sussman (sussman@collab.net) wrote:
> Eric Dorland <er...@mail.mcgill.ca> writes:
>
> > I was thinking about how to implement text-base compression now that
> > compressed streams have been accepted. Looking at the way the config
> > system (since of course I want to make it configurable), I would need
> > to add arguments to svn_wc_get_update_editor and its kin to say
> > whether compression is desired or not. Since this are public
> > functions, this would be an API change. Is the API frozen at this
> > point?
>
> It's a small API tweak... I wouldn't object. I think having an
> (optionally) compressed text-base would be a nice interim compromise,
> until we rewrite libsvn_wc someday.
>
--
Eric Dorland <er...@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+
G e h! r- y+
------END GEEK CODE BLOCK------
Re: Changes to exported symbols
Posted by Ben Collins-Sussman <su...@collab.net>.
Eric Dorland <er...@mail.mcgill.ca> writes:
> I was thinking about how to implement text-base compression now that
> compressed streams have been accepted. Looking at the way the config
> system (since of course I want to make it configurable), I would need
> to add arguments to svn_wc_get_update_editor and its kin to say
> whether compression is desired or not. Since this are public
> functions, this would be an API change. Is the API frozen at this
> point?
It's a small API tweak... I wouldn't object. I think having an
(optionally) compressed text-base would be a nice interim compromise,
until we rewrite libsvn_wc someday.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org