From owner-freebsd-ports@FreeBSD.ORG  Thu Mar 25 16:28:32 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: FreeBSD-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 03F241065670
	for <FreeBSD-ports@freebsd.org>; Thu, 25 Mar 2010 16:28:32 +0000 (UTC)
	(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46])
	by mx1.freebsd.org (Postfix) with ESMTP id DC62D8FC15
	for <FreeBSD-ports@freebsd.org>; Thu, 25 Mar 2010 16:28:31 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 3CA898C07E; Thu, 25 Mar 2010 11:28:31 -0500 (CDT)
Date: Thu, 25 Mar 2010 11:28:31 -0500
From: Mark Linimon <linimon@lonesome.com>
To: Gary Jennejohn <gary.jennejohn@freenet.de>
Message-ID: <20100325162831.GB24672@lonesome.com>
References: <4BAB6135.4030800@rsu.ru>
	<20100325154420.6c91a7b9@ernst.jennejohn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100325154420.6c91a7b9@ernst.jennejohn.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: Freebsd Ports <FreeBSD-ports@freebsd.org>, Alexander Pyhalov <alp@rsu.ru>
Subject: Re: postgres and CVE-2010-0442
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Mar 2010 16:28:32 -0000

On Thu, Mar 25, 2010 at 03:44:20PM +0100, Gary Jennejohn wrote:
> It's only been a week since it was assigned to the maintainer (girgen@)
> to look at.
> 
> It's too soon for a maintainer timeout, although I suppose if this is
> considered to be an enormous security risk it could be committed without
> waiting.

I'd say go ahead and commit it.  We often waive the two-week period for
security problems.

mcl