From owner-freebsd-bugs@FreeBSD.ORG  Mon Feb 28 03:16:30 2011
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 95D48106566B;
	Mon, 28 Feb 2011 03:16:30 +0000 (UTC)
	(envelope-from eadler@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 6D0BA8FC15;
	Mon, 28 Feb 2011 03:16:30 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1S3GUkx069064;
	Mon, 28 Feb 2011 03:16:30 GMT
	(envelope-from eadler@freefall.freebsd.org)
Received: (from eadler@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1S3GTV9069059;
	Sun, 27 Feb 2011 22:16:29 -0500 (EST) (envelope-from eadler)
Date: Sun, 27 Feb 2011 22:16:29 -0500 (EST)
Message-Id: <201102280316.p1S3GTV9069059@freefall.freebsd.org>
To: stb@lassitu.de, eadler@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: eadler@FreeBSD.org
Cc: 
Subject: Re: gnu/137665: [patch] dialog(1) goes into tight loop on
	encountering eof
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2011 03:16:30 -0000

Synopsis: [patch] dialog(1) goes into tight loop on encountering eof

State-Changed-From-To: feedback->suspended
State-Changed-By: eadler
State-Changed-When: Sun Feb 27 22:13:02 EST 2011
State-Changed-Why: 
This is contrib software & should probably be resolved upstream.
Also - behavior reported in PR has been fixed with recent update

http://www.freebsd.org/cgi/query-pr.cgi?pr=137665