Re: svn commit: rev 3010 - trunk/notes

> I should probably start collecting all my patches that will never
> be accepted and post them somewhere (namely jlibtool support,
> entry caching, svn:permissions, etc.).

is there any reason that jlibtool support won't go in? i don't recall
anyone objecting to it when you posted it, and i'd personally be
interested in having it both in apr and in svn for when i'm building
on os x.

and the entry caching was just an issue of the patch not being done,
right? in concept, that is going to happen at some point isn't it? i
know philip was working on things that would make it easier, and the
collab.net guys (karl i think) said something about having that for
1.0 just for performance issues...

-garrett (who'd hate to see all this work go away...)

-- 
garrett rooney                    Remember, any design flaw you're 
rooneg@electricjellyfish.net      sufficiently snide about becomes  
http://electricjellyfish.net/     a feature.       -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org