From owner-freebsd-ports-bugs@FreeBSD.ORG  Mon Sep  1 02:56:50 2014
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 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EC75C617
 for <freebsd-ports-bugs@FreeBSD.org>; Mon,  1 Sep 2014 02:56:50 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D343F1C86
 for <freebsd-ports-bugs@FreeBSD.org>; Mon,  1 Sep 2014 02:56:50 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s812uoDC017428
 for <freebsd-ports-bugs@FreeBSD.org>; Mon, 1 Sep 2014 02:56:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 182209] [new port] emulators/hyperv-ic: Ports containing
 Hyper-V integration components for FreeBSD
Date: Mon, 01 Sep 2014 02:56:51 +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: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kyliel@microsoft.com
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-182209-13-kVK4gf7zGs@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-182209-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-182209-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: Mon, 01 Sep 2014 02:56:51 -0000

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

--- Comment #17 from Kylie <kyliel@microsoft.com> ---
Hi John,

Thanks for feedback. Yes, currently we used one shar file for FreeBSD 9.1 and
the other shar file for FreeBSD 9.2.

To avoid confusion, you see 4 test logs because we tested both 32 bit and 64
bits for each FreeBSD release. 

So we will generate "ONE" shar file for FreeBSD 9.1 and 9.2 and upload it. In
future, if we get ports for FreeBSD 8.4, 9.3 and 10 ready, we will update shar
file. Is that right approach? Thank you.

Thanks,
Kylie

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