From: Markus Armbruster <armbru@redhat.com>
To: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
Cc: Greg Kurz <gkurz@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Implementing 9p for Windows host
Date: Tue, 12 Apr 2016 11:20:00 +0200 [thread overview]
Message-ID: <87fuuri3pb.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <570BB697.7030701@telematik-zentrum.de> (Michael Fritscher's message of "Mon, 11 Apr 2016 16:37:11 +0200")
Michael Fritscher <michael.fritscher@telematik-zentrum.de> writes:
> Hello Greg,
>
> thanks for your answer! Yes, I already jumped in - I was surprised how
> fast it went. I was afraid of much bigger problems ;-) I've a already
> a V2 nearly ready :-) As a teaser: Fixed read/write support and the
> possibility to execute binaries from the mountpoint.
>
> Yes, I decided not to copy the 9p-local.c, because I had to change not
> as many places I thought in the first place.
>
> I'm wondering about the xattr stuff... Perhaps I try to remove the
> <sys/xattr.h> from hw/9pfs/9p-xattr.h and #ifdef the things which are
> broken afterwards. That would have the advantage that I don't have to
> have local function stubs in the 9p-local.c anymore.
>
> To the licence: I asked because I know that other projects have a
> formal process to cope with this - like a written agreement to be
> bound to the license.
We don't do formal CLAs. Instead, we follow the kernel's lead and
require Signed-off-by.
http://wiki.qemu-project.org/Contribute/SubmitAPatch#Patch_emails_must_include_a_Signed-off-by:_line
Please stick to GPLv2+ for new work, unless you have a really good
reason not to.
http://wiki.qemu-project.org/License
prev parent reply other threads:[~2016-04-12 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 11:41 [Qemu-devel] Implementing 9p for Windows host Michael Fritscher
2016-04-11 14:14 ` Greg Kurz
2016-04-11 14:37 ` Michael Fritscher
2016-04-11 14:54 ` Greg Kurz
2016-04-12 9:20 ` Markus Armbruster [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=87fuuri3pb.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=michael.fritscher@telematik-zentrum.de \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.