All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kiarie <davidkiarie4@gmail.com>
To: "Jan Kiszka" <jan.kiszka@siemens.com>,
	"Eric Blake" <eblake@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] update copyright notice
Date: Tue, 5 Mar 2019 18:19:01 +0300	[thread overview]
Message-ID: <CABdVeAAonLbrbDLF2aXmG5Ajss-dyOBf3JjTqFDud7ruADuO0A@mail.gmail.com> (raw)
In-Reply-To: <CABdVeAAWr3F6hN5mtXP9YoA7WvBOzgy-iv3dcZ+4crBfbRmtkA@mail.gmail.com>

On Tue, Mar 5, 2019 at 5:36 PM David Kiarie <davidkiarie4@gmail.com> wrote:

> i hope you don't find this offensive, Eric but i'm forwarding this message
> to all the people on this thread.
>
> i don't find anything exactly private in this email.
>
> [off-list]
>
> On 3/4/19 1:20 PM, David Kiarie wrote:
> > On Mon, Mar 4, 2019 at 8:48 PM Philippe Mathieu-Daudé <philmd@redhat.com
> >
> > wrote:
> >
> >> On 3/4/19 4:18 PM, David Kiarie wrote:
> >>> Signed-off-by: David Kiarie <davidkiarie4@gmail.com>
> >>
> >> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> >>
> >
> > would i be wrong to say this patch received unwarranted scrutiny from
> you,
> > Philippe?
>
> David, please calm down, and don't write emails that can sound like you
> are attacking your reviewers on list.  Assume good intent - Philippe
> reviewed your patch with the same level of scrutiny as many other
> patches he reviews, and his question for your previous patch revision
> about whether you intended to change the copyright year was not an
> attack, but an honest question.
>
> Open source works best when anyone feels like they can contribute.
> Copyright lines are an interesting beast - they carry legal
> significance, so care should be taken that they aren't changed by
> mistake, but at the same time, you do not have to know the code that the
> copyright is protecting to ask an honest question about whether a change
> is intentional.
>

it's simply not fair for me to waiting for you guys to merge this patch. i
sent both, you can pick whichever.


>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc.           +1-919-301-3226
> Virtualization:  qemu.org | libvirt.org
>

  reply	other threads:[~2019-03-05 15:19 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
     [not found]       ` <546a3879-6cf6-b248-c6df-62489730be57@redhat.com>
2019-03-05 14:36         ` [Qemu-devel] Fwd: " David Kiarie
2019-03-05 15:19           ` David Kiarie [this message]
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=CABdVeAAonLbrbDLF2aXmG5Ajss-dyOBf3JjTqFDud7ruADuO0A@mail.gmail.com \
    --to=davidkiarie4@gmail.com \
    --cc=eblake@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --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.