From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Fabio Fantoni <fantonifabio@tiscali.it>
Cc: james.harper@bendigoit.com.au, xen-devel@lists.xensource.com
Subject: Re: Gplpv driver
Date: Mon, 6 Jun 2011 10:53:12 -0400 [thread overview]
Message-ID: <20110606145312.GA29243@dumpdata.com> (raw)
In-Reply-To: <4DEA2609.4070608@tiscali.it>
On Sat, Jun 04, 2011 at 02:33:13PM +0200, Fabio Fantoni wrote:
> Gplpv driver is good project, we use it on many domUs some years,
> actualy on production system mainly gplpv_XP_0.11.0.213.msi on
> windows xp systems and gplpv_Vista2008x64_0.11.0.238.msi on windows
> 7 systems mainly on debian with xen 4.0 dom0s from source
> Unfortunately there are some deficiencies that penalize gplpv, poor
> documentation, poor testing, my knowledge of English is too poor for
> do good and complete documentation but i try to give small help.
> About the testing I saw that there continue to be commit to the
> repository but there are no new builds on
> http://www.meadowcourt.org/downloads/; there are new builds
> elsewhere?
Fabio,
In the future, CC James on these emails.. (which I just did for you)
> For the builds versions I'd recommend to also have a stable branch
> to apply only bugfixes, for example when reach feature add create
> branch 0.12, insert in only this bugfix and continue in mainly
> repository development with 0.13 ecc...
> James Harper, thanks for all the work you do on the gplpv, I hope my
> tips will be of help and I look forward to new builds to test them
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-06-06 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 12:33 Gplpv driver Fabio Fantoni
2011-06-06 14:53 ` Konrad Rzeszutek Wilk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110606145312.GA29243@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=fantonifabio@tiscali.it \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).