From owner-freebsd-ports-bugs@FreeBSD.ORG  Tue May 19 15:02:42 2015
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5CDB9DAA
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 19 May 2015 15:02:42 +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 473D3186B
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 19 May 2015 15:02:42 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4JF2g9N021483
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 19 May 2015 15:02:42 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 198888] net-mgmt/tcptrack FIX, upgrade 1.4.2 ==> 1.4.3, take
 MAINTAINER
Date: Tue, 19 May 2015 15:02:42 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jgh@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198888-13-sLrSoK9HOo@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198888-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-198888-13@https.bugs.freebsd.org/bugzilla/>
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.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2015 15:02:42 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198888

--- Comment #4 from jgh@FreeBSD.org ---
I have come across this situation many times where there is a delay in upstream
acceptance of a patch, which could be for many reasons. In this case, I usually
keep the MASTER_SITES as is, as they are the authority for the software, add
the patch to the ${FILESDIR}, and bump the PORTREVISION. Assuming the patch is
accepted at some point, the patch is removed and the PORTVERSION is bumped to
match the new version which includes your merged patch from the upstream
vendor.

Thanks for your work!

-- 
You are receiving this mail because:
You are the assignee for the bug.