All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kiarie <davidkiarie4@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>, Peter Xu <peterx@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/1] update copyright notice
Date: Mon, 4 Mar 2019 23:11:57 +0300	[thread overview]
Message-ID: <CABdVeAA55u2+vQvzc=6v4sgG8kSokFj6oH6wesYPOc9E_KD10g@mail.gmail.com> (raw)
In-Reply-To: <5659a8f6-d9d1-53b7-5be4-7460590c65d9@redhat.com>

>
> IANAL and I have no knowledge of IOMMU indeed.
> I noticed first this patch is sent from the same email used in this
> copyright notice, then the patch content merged in commit d29a09ca684
> was accepted in 2016 with a copyright date of 2015, hence your copyright
> modification looks correct to me.
>
> Regards,
>
> Philippe.


it looks like i already discarded(in the confusion that issued from Qemu
not being able to merge a simple patch and creating theories around it)
Daniel's review, wouldn't it be unfair to keep yours?


> >
> >
>

  reply	other threads:[~2019-03-04 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 15:18 [Qemu-devel] [PATCH 0/1] update copyright notice David Kiarie
2019-03-04 15:18 ` [Qemu-devel] [PATCH 1/1] " David Kiarie
2019-03-04 17:48   ` Philippe Mathieu-Daudé
2019-03-04 19:20     ` David Kiarie
2019-03-04 19:29       ` David Kiarie
2019-03-04 19:30         ` David Kiarie
2019-03-04 19:36           ` David Kiarie
2019-03-04 20:01         ` Philippe Mathieu-Daudé
2019-03-04 20:11           ` David Kiarie [this message]
     [not found]       ` <546a3879-6cf6-b248-c6df-62489730be57@redhat.com>
2019-03-05 14:36         ` [Qemu-devel] Fwd: " David Kiarie
2019-03-05 15:19           ` [Qemu-devel] " David Kiarie
2019-03-04 20:52 ` [Qemu-devel] [PATCH v4? 0/1] " Eric Blake
2019-03-05 14:16   ` David Kiarie
2019-03-05 14:30     ` David Kiarie

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='CABdVeAA55u2+vQvzc=6v4sgG8kSokFj6oH6wesYPOc9E_KD10g@mail.gmail.com' \
    --to=davidkiarie4@gmail.com \
    --cc=berrange@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.