Hi Josh,
The two projects (/bin/ksh & /sbin/sh migration to ksh93) are closely related
and are likely to involve some of the same people. Unfortunately we
don't have the engineering resources to do this work now.
Sorry,
April
> DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-t
ype:content-transfer-encoding:content-disposition:references;
b=UVa6GpDwMWxSmV0Vne3RD7dUwgSky+2buAF3bwZTAOoRhd6NghP459sBujMTMQuRsiZ3rdFGeG6y1c
TiysXpOyCXPXbyfQWPdPM3KbbsjqVWzx+Rw0kWWrzOyJe/7uTCcpH0lTg7BEbRML45XYYjpE3q/wUj42
6QetQDppXkSrY=
> Date: Thu, 17 Aug 2006 18:49:18 +0200
> From: "Josh Hurst" <joshhurst at gmail.com>
> To: "April Chin" <April.Chin at eng.sun.com>, "Korn Shell 93
integration/migration project discussion"
<ksh93-integration-discuss at opensolaris.org>
> Subject: Re: [ksh93-integration-discuss] ksh93 for /bin/sh?
> Cc: martin.schaffstall at googlemail.com, hlangeveld at mailworks.org
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> On 8/14/06, April Chin <April.Chin at eng.sun.com> wrote:
> > I agree that we need to focus on the ksh93 integration and /bin/ksh
> > migration first. I don't think I'm ready to discuss ksh93 migration
> > to /bin/sh at this point.
> What about assigning this bin/sh migration project to another engineer at Sun?
> --
> Josh
