From owner-freebsd-ports-bugs@FreeBSD.ORG  Tue Dec 23 00:10:42 2014
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
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 82D198FA
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 23 Dec 2014 00:10: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 695E03890
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 23 Dec 2014 00:10: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 sBN0AgDA020530
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 23 Dec 2014 00:10:42 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 196185] emulators/hyperv-is: Update Hyper-V ports for FreeBSD
 10.1
Date: Tue, 23 Dec 2014 00:10:42 +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-patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kyliel@microsoft.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback+
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-196185-13-WT6lhbfm2a@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196185-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-196185-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.18-1
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, 23 Dec 2014 00:10:42 -0000

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

--- Comment #4 from Kylie <kyliel@microsoft.com> ---
Jun, please attach patch here. 

Hi Xin, 

Ports are available for all new releases. However when 10.2 is released, we may
already get everything upstreamed and nothing is needed for 10.2. Then for
10.2, how to exit gracefully without error message if somebody still tries to
run our ports. 
We could add one message to say "no more update for 10.2" but ERROR will still
be printed if we exits ports with "IGNORE" signal. 

Thanks,
Kylie Liang

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