From owner-freebsd-ports-bugs@freebsd.org  Thu Nov 12 14:19:13 2015
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81C97A2C9EC
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Thu, 12 Nov 2015 14:19:13 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
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 65E3517A2
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 12 Nov 2015 14:19:13 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tACEJD0v034701
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 12 Nov 2015 14:19:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 204493] Update for sysutils/vm-bhyve
Date: Thu, 12 Nov 2015 14:19:13 +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 Some People
X-Bugzilla-Who: koobs@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-204493-13-cEBvZeeAXm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204493-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-204493-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: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 14:19:13 -0000

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

--- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> ---
@Churchers thanks for your submission.

All else being equal, it's almost always good to target:

1) Only one attachment with changes. Sometimes multiple versions of a patch are
submitted. In your case there is a shar of the directory and a diff to svn

Attachment authors/submitters should 'obsolete' any that are no longer relevant
or they dont want a FreeBSD committer to reference. You can do so by clicking
Attachment Details -> Edit Details -> [X] Obsolete.

2) shars are only appropriate for "new" ports, unified diffs for everything
else

So from here:

* obsolete the attachment that you don't want a committer to reference
* set maintainer-approval to "+" on the attachment that you do

My guess is it's attachment 163043, as attachment 163041 is a shar (should be a
diff for updates) and is older than the former.

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