Anthony Towns wrote:
> If it's not to enable backwards and cross-Unix compatability, why do we
> care about POSIX at all?
> bash, /bin/echo and POSIXLY_CORRECT /bin/echo all treat "\c" as a literal,
> for reference.
GNU has always adopted the BSD behaviour of not interpreting back
slashes. All
On Sat, Jun 22, 2002 at 09:29:42PM +1000, Anthony Towns wrote:
> Sorry, but this doesn't follow. Treating "serious" as a severity or a
> tag is largely immaterial, and the fundamental point of the "serious"
> severity or tag is as an aid to release management.
That may be its intent, but apparentl
On Sat, Jun 22, 2002 at 02:02:00AM -0500, Manoj Srivastava wrote:
> >>"Branden" == Branden Robinson <[EMAIL PROTECTED]> writes:
> Branden> * "Release critical bugs are _very_ rare."; and
> Branden> * Release critical bugs should be the domain of the Release Manager,
> Branden> Then we really don
On Sat, Jun 22, 2002 at 03:06:38AM -0400, Clint Adams wrote:
> > As far as I can tell there are two possibilities here:
> > (a) "it" is pdksh or posh, and it already works at least as well
> > as ash on the various #!/bin/sh scripts in Debian, or
> It is pdksh.
> > (b) "it" is pdksh
>>"Branden" == Branden Robinson <[EMAIL PROTECTED]> writes:
Branden> If:
Branden> * "Release critical bugs are _very_ rare."; and
Branden> * Release critical bugs should be the domain of the Release Manager,
Branden> Then we really don't need a tight connection between the
Branden> "serious
> As far as I can tell there are two possibilities here:
>
> (a) "it" is pdksh or posh, and it already works at least as well
> as ash on the various #!/bin/sh scripts in Debian, or
It is pdksh.
> (b) "it" is pdksh or posh or similar, and it doesn't yet work as
>
> Any chance of a rerun with posh (sources are in queue/new and readable)
> or pdksh?
I don't think you'll be able to gauge posh that way; shoop isn't
POSIX-compliant.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
7 matches
Mail list logo
