From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Dec 28 19:31:21 2004 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B7EE16A4CE for ; Tue, 28 Dec 2004 19:31:21 +0000 (GMT) Received: from smtp.rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7109743D41 for ; Tue, 28 Dec 2004 19:31:20 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: (qmail 26863 invoked by uid 89); 28 Dec 2004 19:38:10 -0000 Received: from unknown (HELO it.buh.tecnik93.com) (81.196.204.98) by 0 with SMTP; 28 Dec 2004 19:38:10 -0000 Received: from it.buh.tecnik93.com (localhost.buh.tecnik93.com [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id 804521187D; Tue, 28 Dec 2004 21:31:13 +0200 (EET) Date: Tue, 28 Dec 2004 21:31:09 +0200 From: Ion-Mihai Tetcu To: pav@FreeBSD.org Message-ID: <20041228213109.6ed4e952@it.buh.tecnik93.com> In-Reply-To: <1104261378.48118.11.camel@hood.oook.cz> References: <200412281659.iBSGxciD076228@freefall.freebsd.org> <20041228211134.056bb9b3@it.buh.tecnik93.com> <1104261378.48118.11.camel@hood.oook.cz> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: jpeg@thilelli.net cc: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/75551: [PATCH] Correct a 'post-patch' entry in the port's Makefile since a files/patch-* seems to do the same thing. X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 19:31:21 -0000 On Tue, 28 Dec 2004 20:16:17 +0100 Pav Lucistnik wrote: > Ion-Mihai Tetcu p=ED=B9e v =FAt 28. 12. 2004 v 21:11 +0200: > > On Tue, 28 Dec 2004 16:59:38 GMT > > Pav Lucistnik wrote: > >=20 > > > Synopsis: [PATCH] Correct a 'post-patch' entry in the port's Makefile= since a files/patch-* seems to do the same thing. > > >=20 > > > State-Changed-From-To: open->closed > > > State-Changed-By: pav > > > State-Changed-When: Tue Dec 28 16:59:05 GMT 2004 > > > State-Changed-Why:=20 > > > Maintainer promised to integrate this patch into his next update. > >=20 > > Pav, why is the state "close" more appropriate that analyzed ? > > I mean I could forget about them ;) >=20 > First, I trust you that you will not forget about them. >=20 > Second, I fear that those PRs would be forgotten in analyzed state once > the port is updated and the matter settled. So I rather closed them. I try not to forget to say about the PRs that should be closed when my PRs supersede them. > > > (Bottom line here is that you should approach maintainer directly, > > > without the detour via send-pr) > >=20 > > For two stylistic ones yes, but for the dir permissions (75549) and > > "UntrustedDeliveryAgent" and "QuarantineAgent (75548), I tend to > > believe a pr is OK. >=20 > Always, always, always, when there is an active maintainer around, > direct contact with a maintainer is strongly preferred. >=20 > It's really an ugly habit to send-pr patch and Cc maintainer. Better that send pr and not cc the maintainer, anyway. > First, a lot of maintainers don't know how to act properly on such > emails, they just don't Cc their replies back to GNATS. I think the problem is that the subj, must begin with FreeBSD-gnats-submit@FreeBSD.org or else it becomes a 'misfiled' reply. Only cc'ing seems not to be enough. > And in last row, it creates a lot of administrative overhead for us, > committers. True. --=20 IOnut Unregistered ;) FreeBSD "user"