From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Oct 1 10:43:43 2014 Return-Path: Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD435B8F for ; Wed, 1 Oct 2014 10:43:43 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C4DBCE72 for ; Wed, 1 Oct 2014 10:43:43 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s91AhhDR042643 for ; Wed, 1 Oct 2014 10:43:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 192907] www/fcgiwrap: Update 1.1.0-5 Date: Wed, 01 Oct 2014 10:43:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd@skysmurf.nl X-Bugzilla-Status: Patch Ready X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 10:43:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192907 --- Comment #15 from A.J. "Fonz" van Werven --- The summary/title has never been right in the first place and doesn't reflect what the submitter's patch does either. Anyway, as far as I can see, I can't change the summary/title myself. That's probably committer's prerogative. But if you need a suggestion, I'd say something like: "Improved handling of binary stripping and addition of a new command line option that restricts what may be run" ought to cover it nicely. Or, if you like it shorter, replace the second part with simply "addition of a new feature". -- You are receiving this mail because: You are the assignee for the bug.