"Steve Dwire" <sdwire@pcsigroup.com> writes:
> Aha. It is there in the FAQ. I guess I kind of viewed IssueTracker as
> "the" place to track things that need to be addressed for a particular
> release of Subversion. The workaround presented in the FAQ, though, is
> a patch to the source code.
>
> What do people think? Is a source code patch an acceptable workaround
> for the 1.0 release to end users? Or should the patch become part of
> the 1.0 product, in spite of the ugly #ifdef and the
> duct-tape-and-baling-wire solution it contains?
>
> Personally, I'd prefer to see the official 1.0 release do "the best it
> can" with this issue, rather than sticking the poor end users with an
> "Oh, you can patch your source and rebuild the product" workaround. Is
> that likely without an official issue filed?
I'm not sure we're confident enough about that patch (that it solves
the problem) to put it in mainline Subversion. It would suck to have
something so ugly in the code and yet *still* have the problem --
whereas no one minds so much if it's just an experimental workaround.
Wish we had a better sense of how often users run into the problem...
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 20 21:22:27 2003