qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Kiarie <davidkiarie4@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Jan Kiszka" <jan.kiszka@siemens.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Alexandro Sánchez Bach" <alexaltea123@gmail.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"Thomas Huth" <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] hw/i386: update copyright notice
Date: Mon, 4 Mar 2019 18:22:17 +0300	[thread overview]
Message-ID: <CABdVeADEkyu20gB58pLgsPSCM23dPb+VgVtGOKR6XaX8=orwkg@mail.gmail.com> (raw)
In-Reply-To: <CABdVeAD2mfUR5-29NQ=jkWjLRt6wyQNJEk4hFOZYFsnKCgYZFg@mail.gmail.com>

On Mon, Mar 4, 2019 at 6:13 PM David Kiarie <davidkiarie4@gmail.com> wrote:

>
>
>
>>>>>>>
>>>>>>> Hi David,
>>>>>>>>
>>>>>>>> On 2/23/19 11:54 AM, David Kiarie wrote:
>>>>>>>> > Signed-off-by: David Kiarie <davidkiarie4@gmail.com>
>>>>>>>> > ---
>>>>>>>> >  hw/i386/amd_iommu.c | 2 +-
>>>>>>>> >  hw/i386/amd_iommu.h | 2 +-
>>>>>>>> >  2 files changed, 2 insertions(+), 2 deletions(-)
>>>>>>>> >
>>>>>>>> > diff --git a/hw/i386/amd_iommu.c b/hw/i386/amd_iommu.c
>>>>>>>> > index 8ad707a..4f179da 100644
>>>>>>>> > --- a/hw/i386/amd_iommu.c
>>>>>>>> > +++ b/hw/i386/amd_iommu.c
>>>>>>>> > @@ -2,7 +2,7 @@
>>>>>>>> >   * QEMU emulation of AMD IOMMU (AMD-Vi)
>>>>>>>> >   *
>>>>>>>> >   * Copyright (C) 2011 Eduard - Gabriel Munteanu
>>>>>>>> > - * Copyright (C) 2015 David Kiarie, <davidkiarie4@gmail.com>
>>>>>>>> > + * Copyright (C) 2016 David Kiarie Kahurani
>>>>>>>>
>>>>>>>> Why do you change the year? Because your work was merged in 2016?
>>>>>>>>
>>>>>>>
>>>>>>> no.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> though, if you have a legitimate issue with the change, you can
>>>>>> always air it.
>>>>>>
>>>>>
>>>>> you might think random emails are weird but Paolo, i don't expect to
>>>>> see any activity from you, on Qemu repo before this issue is sorted ;-)
>>>>>
>>>>
>>>> i mostly don't care about this code but i *wrote* it. if i am not
>>>> allowed even make such minor(which i not a routine), why shouldn't i ask
>>>> you to take the files down?
>>>>
>>>
>>> or, rather, a small issue turns into a scene about how clean Qemu is.
>>> why not take down all my dirty code?
>>>
>>
>> look i'm resending this patch and next time we're having this
>> conversation, i'll be defacing qemu.
>>
>
>
> either you have to update my code to what i think it should look like or
> you have to take down - wtf
>
> then you try to cook rubbish over it.
>

being a maintainer makes you special but let's see if you'll have something
to maintain.



>
>
>>
>>
>>>
>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>> >   *
>>>>>>>> >   * This program is free software; you can redistribute it and/or
>>>>>>>> modify
>>>>>>>> >   * it under the terms of the GNU General Public License as
>>>>>>>> published by
>>>>>>>> > diff --git a/hw/i386/amd_iommu.h b/hw/i386/amd_iommu.h
>>>>>>>> > index c52886f..cb258a7 100644
>>>>>>>> > --- a/hw/i386/amd_iommu.h
>>>>>>>> > +++ b/hw/i386/amd_iommu.h
>>>>>>>> > @@ -2,7 +2,7 @@
>>>>>>>> >   * QEMU emulation of an AMD IOMMU (AMD-Vi)
>>>>>>>> >   *
>>>>>>>> >   * Copyright (C) 2011 Eduard - Gabriel Munteanu
>>>>>>>> > - * Copyright (C) 2015 David Kiarie, <davidkiarie4@gmail.com>
>>>>>>>> > + * Copyright (C) 2016 David Kiarie Kahurani
>>>>>>>> >   *
>>>>>>>> >   * This program is free software; you can redistribute it and/or
>>>>>>>> modify
>>>>>>>> >   * it under the terms of the GNU General Public License as
>>>>>>>> published by
>>>>>>>> >
>>>>>>>>
>>>>>>>

  reply	other threads:[~2019-03-04 15:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 10:54 [Qemu-devel] [PATCH 0/1] update copyright notice David Kiarie
2019-02-23 10:54 ` [Qemu-devel] [PATCH 1/1] hw/i386: " David Kiarie
2019-02-25 10:38   ` Daniel P. Berrangé
2019-03-04 11:22     ` David Kiarie
2019-03-04 11:41       ` David Kiarie
2019-03-04 11:44       ` Paolo Bonzini
2019-03-04 11:46         ` David Kiarie
2019-03-04 11:57   ` Philippe Mathieu-Daudé
2019-03-04 12:57     ` David Kiarie
2019-03-04 13:42       ` David Kiarie
2019-03-04 14:10         ` David Kiarie
2019-03-04 14:36           ` David Kiarie
2019-03-04 14:40             ` David Kiarie
2019-03-04 15:06               ` David Kiarie
2019-03-04 15:13                 ` David Kiarie
2019-03-04 15:22                   ` David Kiarie [this message]
2019-03-04 15:24                     ` David Kiarie
2019-03-04 15:23                   ` Thomas Huth
2019-03-04 15:27                     ` David Kiarie
2019-03-04 15:32                       ` David Kiarie
2019-03-04 15:33                         ` David Kiarie
2019-03-04 15:39                           ` David Kiarie
2019-03-04 16:29                             ` 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='CABdVeADEkyu20gB58pLgsPSCM23dPb+VgVtGOKR6XaX8=orwkg@mail.gmail.com' \
    --to=davidkiarie4@gmail.com \
    --cc=alexaltea123@gmail.com \
    --cc=ehabkost@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 \
    --cc=thuth@redhat.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).