Well, we seem to be coming back to this in other threads.
What would we like to do about entries caching?
- Fix libsvn_wc in one swoop to correctly pass the admin_baton
everywhere.
Status: Posted an incomplete broken patch that starts the
conversion process.
Pro: Everything gets fixed.
Con: I don't have the time to complete this, so this would have to
fall to someone else.
- Branch off and commit the broken patch.
Pro: If someone steps up, they can pick up the pieces.
Con: Unlikely to work and I can't see the branch through anyway,
so the branch is likely to get out-of-date quickly.
- Add a caching-only API
Status: Patches posted (if what I posted before doesn't cleanly
apply, it'd be fairly easy to make it clean again).
Pro: Allows us to incrementally address the API concerns without
forcing to change the entirety of libsvn_wc.
Con: Philip has stated he is very much against this. I believe he
may have even vetoed this.
I'd like to see the caching hit before 1.0, but since I have a life
outside of SVN, I just can not devote the time to change all of
libsvn_wc. Everytime I try to put aside time to it, I just cry when
I look at it. In the limited time I have, I'd like to address more
attainable goals (such as getting svn-config to work properly when
we have in-tree dependencies).
Thoughts? -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 11 19:49:58 2002