Nothing on the C side. My changes are still in-progress and are API breaking in major ways (and more API changes coming before we're ready for 1.4).
I've no idea about the C++ side. - Bruce On Fri, Jun 4, 2010 at 9:58 PM, Jeff Hammerbacher <[email protected]>wrote: > Thanks! C or C++ folks? I might try my hand at the merge this morning, > since > there are only three total patches there, but I'd prefer if you guys chimed > in. I'm cutting the release at noon. > > On Thu, Jun 3, 2010 at 10:40 PM, Jeff Hodges <[email protected]> wrote: > > > Ruby side is merged into branch-1.3. > > -- > > Jeff > > > > On Tue, Jun 1, 2010 at 11:13 AM, Doug Cutting <[email protected]> > wrote: > > > On 06/01/2010 11:06 AM, Jeff Hammerbacher wrote: > > >>> > > >>> So, rather than maintaining this incrementally, you want to move all > of > > >>> these en-masse? That's fine with me, if you want to take on keeping > > this > > >>> straight. To my thinking, it's simpler to maintain this as we go. > > >> > > >> Should be a simple copy-paste from the CHANGES.txt in branch-1.3, no? > > > > > > You'll have to also then find each message that was pasted and remove > it > > > from the 1.4.0 section. Not a big deal. > > > > > > Another reason to update-as-we-go is to better track of what's been > > merged > > > and what's not. If the CHANGES.txt in trunk and the branch disagree > then > > > folks have to know which takes precedence. > > > > > > Doug > > > > > >
