From owner-freebsd-ports@FreeBSD.ORG Tue May 6 19:06:30 2008 Return-Path: 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 36EB0106564A for ; Tue, 6 May 2008 19:06:30 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id 10A098FC22 for ; Tue, 6 May 2008 19:06:30 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id B71385C60; Tue, 6 May 2008 15:10:41 -0400 (EDT) Date: Tue, 6 May 2008 15:10:41 -0400 From: Wesley Shields To: Paul Schmehl Message-ID: <20080506191041.GE95361@atarininja.org> References: <5D3D858C70DC91D03AAC364F@utd65257.utdallas.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5D3D858C70DC91D03AAC364F@utd65257.utdallas.edu> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: ports@FreeBSD.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2008 19:06:30 -0000 On Mon, May 05, 2008 at 10:54:59AM -0500, Paul Schmehl wrote: > 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? Reply to bug-followup@ leaving the subject intact. Usually it is "Re: ports/XXXXX " which is enough to get it routed into the correct PR. You can attach your new patch directly to that mail and it will be handled properly. I think it takes most people a few times of trial and error to get it right, so don't feel bad. I know I opened a few PRs by mistake that way. :) -- WXS