From owner-freebsd-ports@FreeBSD.ORG  Mon Jan 14 17:40:13 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 9930F1AA
 for <freebsd-ports@freebsd.org>; Mon, 14 Jan 2013 17:40:13 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 by mx1.freebsd.org (Postfix) with ESMTP id 569EB8A2
 for <freebsd-ports@freebsd.org>; Mon, 14 Jan 2013 17:40:13 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1Tuo12-000PR6-5s; Mon, 14 Jan 2013 18:40:08 +0100
Date: Mon, 14 Jan 2013 18:40:08 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Fernando =?iso-8859-1?Q?Apestegu=EDa?= <fernando.apesteguia@gmail.com>
Subject: Re: Regarding portscout
Message-ID: <20130114174008.GF8239@home.opsec.eu>
References: <CAGwOe2bN_yKytaUYWtc-G0wVkfTZDwHZj8U8ESoeWPAnwhp11A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGwOe2bN_yKytaUYWtc-G0wVkfTZDwHZj8U8ESoeWPAnwhp11A@mail.gmail.com>
Cc: freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Mon, 14 Jan 2013 17:40:13 -0000

Hi!

> In this case, should a maintainer wait until the previous PR is taken
> care of? I didn't read information regarding this in the handbook.

The maintainer should not wait for the previous PR. He can update his PR
with a new patch for the new version, so that the committer can just
commit the newer patch.

-- 
pi@opsec.eu            +49 171 3101372                         7 years to go !