Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Jun 2001 01:36:22 -0400
From:      Garance A Drosihn <drosih@rpi.edu>
To:        obrien@FreeBSD.org
Cc:        Garance A Drosehn <gad@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/bin/sh eval.c
Message-ID:  <p05100e08b73e27b5d8ac@[128.113.24.47]>
In-Reply-To: <20010601123333.A4533@dragon.nuxi.com>
References:  <200106010007.f5107AY14009@freefall.freebsd.org> <20010531231614.A64344@dragon.nuxi.com> <p05100e00b73d683af6e4@[128.113.24.47]> <20010601123333.A4533@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:33 PM -0700 6/1/01, David O'Brien wrote:
>On Fri, Jun 01, 2001 at 12:14:48PM -0400, Garance A Drosihn wrote:
>>  At 11:16 PM -0700 5/31/01, David O'Brien wrote:
>>  >On Thu, May 31, 2001, Garance A Drosehn wrote:
>>  >  >   Modified files:
>>  >>      bin/sh               eval.c
>>  >>    Log:
>>  >  >   Fix how /bin/sh handles 'for' and 'case' statements when it is
>>  >  >   called to do errexit (-e) processing.
>>  >
>>  >Was this reviewed by cracauer?  He has been doing the care and
>>  >feeding of ash for along time and he really up on the subtleties
>>  >of the various standards that address `sh'.
>>
>>  I sent a message on Monday, but haven't received a reply.
>
>A 3 day timeout is not reasonable in our environment.

The change adds two lines, which in the context of the routine are
pretty safe lines to add.  There is even a comment later in the
routine which says

	* XXX - Like "!(n->type == NSEMI)", more types will
	* probably need to be excluded from this test. It's
	* probably better to set or unset EV_TESTED in the
	* loop above than to bloat the conditional here.

I'll back it out if people are really bothered by it, but I
am confident that it's a safe change to make, and I know it
fixes '-e' processing in some situations where I am certain
that ash was not doing the correct thing.

I do not intend to MFC this for at least two weeks, and given
the way my schedule goes that is more likely to end up being
three or four weeks.  Would it make people feel comfortable
enough if I expand that to say that I won't MFC it until
cracauer has ok'ed it?

-- 
Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05100e08b73e27b5d8ac>