From owner-freebsd-ports-bugs@FreeBSD.ORG Thu May 1 20:40:01 2014 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 77A0AEA9 for ; Thu, 1 May 2014 20:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 651A51991 for ; Thu, 1 May 2014 20:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s41Ke1qi015733 for ; Thu, 1 May 2014 20:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s41Ke1N7015732; Thu, 1 May 2014 20:40:01 GMT (envelope-from gnats) Date: Thu, 1 May 2014 20:40:01 GMT Message-Id: <201405012040.s41Ke1N7015732@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Dreamcat4 Subject: Re: ports/189120: [Maintainer update] sysutils/qjail maintenance & enhancements X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Dreamcat4 List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 20:40:01 -0000 The following reply was made to PR ports/189120; it has been noted by GNATS. From: Dreamcat4 To: bug-followup@freebsd.org, qjail@a1poweruser.com Cc: Subject: Re: ports/189120: [Maintainer update] sysutils/qjail maintenance & enhancements Date: Thu, 1 May 2014 21:34:48 +0100 --089e0158ad3802af8f04f85c9b8d Content-Type: text/plain; charset=UTF-8 Thanks. It's just a very small change, but fixes my issue. Please consider that matter resolved in the latest update. --089e0158ad3802af8f04f85c9b8d Content-Type: text/html; charset=UTF-8
Thanks. It's just a very small change, but fixes my issue. Please consider that matter resolved in the latest update.
--089e0158ad3802af8f04f85c9b8d--