From owner-freebsd-ports@FreeBSD.ORG  Fri Sep 10 23:24:36 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EC5CD16A4CE
	for <ports@freebsd.org>; Fri, 10 Sep 2004 23:24:36 +0000 (GMT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B8E9343D31
	for <ports@freebsd.org>; Fri, 10 Sep 2004 23:24:36 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 4684B14316; Fri, 10 Sep 2004 18:24:36 -0500 (CDT)
Date: Fri, 10 Sep 2004 18:24:36 -0500 (CDT)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Willem Jan Withagen <wjw@withagen.nl>
In-Reply-To: <414224EF.6040705@withagen.nl>
Message-ID: <Pine.LNX.4.44.0409101822010.9581-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Walter Venable <weaseal@hotmail.com>
cc: ports@freebsd.org
cc: barner@in.tum.de
Subject: Re: submitting changes to a port
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
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: Fri, 10 Sep 2004 23:24:37 -0000

On Sat, 11 Sep 2004, Willem Jan Withagen wrote:

> Walter Venable wrote:
> 
> > There are also wonderful tools just for port submitters.  Check out 
> > the "porttools" port.
> 
> I've looked at it, and though it makes some things clear.
> It does not get me where I want to go:
>     a new (second) submission of  a PR with patchfiles.

The preferred way to deal with this (IMHO) is to instead send a followup
to the original PR with the new sharfile.  Alternatively, just mention
in the second PR's Synopsis that it obsoletes the first one (e.g.
'supercedes ports/77777').  That way myself or one of the other ports
committers will know to close that one.

mcl