From owner-freebsd-ports@FreeBSD.ORG  Tue May  6 18:59:47 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8D532106564A
	for <ports@FreeBSD.org>; Tue,  6 May 2008 18:59:47 +0000 (UTC)
	(envelope-from pauls@utdallas.edu)
Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.20.110])
	by mx1.freebsd.org (Postfix) with ESMTP id 6B2578FC16
	for <ports@FreeBSD.org>; Tue,  6 May 2008 18:59:47 +0000 (UTC)
	(envelope-from pauls@utdallas.edu)
Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtp3.utdallas.edu (Postfix) with ESMTPSA id B5D7B2420D
	for <ports@FreeBSD.org>; Mon,  5 May 2008 10:54:59 -0500 (CDT)
Date: Mon, 05 May 2008 10:54:59 -0500
From: Paul Schmehl <pauls@utdallas.edu>
To: ports@FreeBSD.org
Message-ID: <5D3D858C70DC91D03AAC364F@utd65257.utdallas.edu>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 
Subject: What's the proper procedure for responding to PRs with patches?
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: Tue, 06 May 2008 18:59:47 -0000

A PR was submitted recently regarding a problem with a port that I maintain.  I 
deteremined what the problem was and created a patch for the Makefile and a 
replacement for one of the patch files in FILESDIR.  I then started send-pr, 
changed the TO; address to bug-followups and added a subject line referring to 
the existing PR.

A new PR was opened anyway.  Obviously I don't know how to do this correctly. 
What is the correct procedure when you want to respond to an existing PR by 
submitting a patch for the problem?

-- 
Paul Schmehl (pauls@utdallas.edu)
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/