Fixed in r17290.
On 11/9/05, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 11/9/05, Ben Collins-Sussman <sussman@red-bean.com> wrote:
>
> > It seems sloppy. Why wouldn't we be following our own
> > conventions/rules about svn_foo_ and svn_foo__ ? Is this some special
> > exception? In other words, if I were to commit a fix for this right
> > now (making svn_txdelta_compose_windows() into a public API), would
> > someone object? Or is there some secret mainteance-nightmare reason
> > *not* to do so? It's not clear to me if this is an intentional thing,
> > or just a bit of sloppiness nobody's bothered to clean up.
>
> ENOCLUE, but it's been that way for a very long time, IIRC.
>
> -garrett
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 10 19:27:00 2005