Re: OS/2 port child work space os2port01

> really? I thought this was not a problem, otherwise it was better for
> me to upgrade my code here before committing.

It is important to have the code inside. Migrating it to newer master/=20=

milestone is way easier then.

> I did not upgrade the OS/2 port to 2.1/2.2 because I was planning to
> wait code integration; but if this is not likely to happen, I will =20
> have
> to merge code again and open a new cws, making the current one =20
> useless.

I had a quick look at your changes and they are very clear and you =20
are very good at separating changes to OS2 only so I think it will be =20=

very easy to migrate to new master.
--=20
Pavel Jan=EDk
[email protected]