Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Apr 2013 12:07:47 -0600
From:      Peter Grehan <grehan@freebsd.org>
To:        freebsd-virtualization@freebsd.org
Cc:        "Abhishek Gupta \(LIS\)" <abgupta@microsoft.com>
Subject:   Importing the Microsoft hyper-v PV drivers into CURRENT
Message-ID:  <51781F73.1070605@freebsd.org>
In-Reply-To: <CADFB2gyMivR6SXJHppYKCFyRVRAiO3HesuTFgZQzfW=-mS5%2B-g@mail.gmail.com>
References:  <CADFB2gwLvnRLzL5VBOYSWURduW3j6y9=VqGO8LVtOfGkgQdWTQ@mail.gmail.com> <5176C98B.4050607@FreeBSD.org> <CADFB2gyMivR6SXJHppYKCFyRVRAiO3HesuTFgZQzfW=-mS5%2B-g@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi all,

  I'd like to start the process of bringing in Microsoft's hyper-v 
paravirtualized drivers into CURRENT. Here're the steps I'll follow:

  1.  Pull the hyperv driver-only git export 
(https://github.com/FreeBSDonHyper-V/VendorBranchForFreeBSDonHyper-V) 
into a vendor branch

  2.  A project branch off CURRENT will be created, and the vendor 
branch pulled into that. Folk can use that for testing/review until it's 
considered OK.

  3.  Lastly, when it's deemed ready, I'll drop the vendor branch into 
CURRENT and retire the project branch.

  Let me know if that sounds OK.

later,

Peter.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51781F73.1070605>