On 11/14/05, Garrett Rooney <email@example.com> wrote:
> So there appear to have been a fair number of fixes merged into the
> 1.3.x branch since rc2 was rolled. Since we haven't even officially
> released rc2 to the world yet, would it make sense to roll an rc3 to
> pick them up.
> Off the top of my head, at least one of the fixes was for a crash bug,
> one was to maintain a feature we had in 1.2.x, and there were several
> fixes for annoying bugs found by the GCC developers. I don't see any
> reason to not have these fixes in 1.3.0.
r17257 is an important fix, which is necessary in order for our SWIG
bindings to compile with GCC 2.95.x.
> There's one major fix remaining in status that hasn't been approved
> yet (the JavaHL reentrant calls thing), and if some of the JavaHL
> people could decide if that should or shouldn't be moved, that would
> be great, but other than that we seem to be pretty much caught up on
> the critical fixes waiting to be merged front.
r17279 is also quite important and is still waiting in STATUS. This
fix removes recursive symbolic links from our build tree, thus solving
1. Python recursively imports modules, such that "libsvn.core"
imports "libsvn.libsvn.core", and "libsvn.libsvn.core" imports
"libsvn.libsvn.libsvn.core", and so on.
2. The Subversion build tree can't be copied from one machine to
another using "scp", because "scp" enters into an infinite copying
loop when it sees recursive symbolic links.
I think it would be a very good idea to include this fix in 1.3.0.
David James -- http://www.cs.toronto.edu/~james
Received on Tue Nov 15 19:05:46 2005