The create_listen_thread code should be on both the trunk and v1.2 branch
right now. You are correct that the heterogeneous fixes haven't moved
just yet, because they aren't quite right. Hope to have that fixed in the
near future...
brian
On Wed, 25 Oct 2006, Ralph H Castain wrote:
There
There are a number of things in the trunk that haven't been moved over to
1.2 branch yet. They are coming shortly, though...once the merge is done,
you might get a few more conflicts, but it shouldn't be too bad.
On 10/25/06 7:06 AM, "Adrian Knoth" wrote:
> On Wed, Oct 25, 2006 at 02:48:33PM +0
On Wed, Oct 25, 2006 at 02:48:33PM +0200, Adrian Knoth wrote:
> > I don't see any new component, Adrian. There have been a few updates to the
> > existing component, some of which might cause conflicts with the merge, but
> > those shouldn't be too hard to resolve.
> Ok, I just saw something with
On Wed, Oct 25, 2006 at 06:27:47AM -0600, Ralph H Castain wrote:
> I don't see any new component, Adrian. There have been a few updates to the
> existing component, some of which might cause conflicts with the merge, but
> those shouldn't be too hard to resolve.
Ok, I just saw something with "cre
I don't see any new component, Adrian. There have been a few updates to the
existing component, some of which might cause conflicts with the merge, but
those shouldn't be too hard to resolve.
As far as I know, the oob/tcp component is relatively stable. Brian is doing
some work on it to enable us
Hi,
I've seen a new oob/tcp component in the v1.2 branch (copied from
the trunk). Of course, it doesn't merge with my IPv6 patch, so
I'm currently using the old oob/tcp in my branch.
Is this new component considered stable, thus making it worth
to port the IPv6 patch?
--
mail: a...@thur.de