qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 1/1] hw/i386: update copyright notice


From: David Kiarie
Subject: Re: [Qemu-devel] [PATCH 1/1] hw/i386: update copyright notice
Date: Mon, 4 Mar 2019 19:29:09 +0300

>
>
>>>>
>>>> On 04/03/2019 16.13, David Kiarie wrote:
>>>>> >
>>>>> >                             Hi David,
>>>>> >
>>>>> >                             On 2/23/19 11:54 AM, David Kiarie wrote:
>>>>> >                             > Signed-off-by: David Kiarie
>>>>> >                             <address@hidden
>>>>> >                             <mailto:address@hidden>>
>>>>> >                             > ---
>>>>> >                             >  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,
>>>>> >                             <address@hidden
>>>>> >                             <mailto:address@hidden>>
>>>>> >                             > + * 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.
>>>>>
>>>>> Hey, calm down. Paolo said that he'd queue your patch, so it will
>>>>> eventually get applied. But that just might take some time, the
>>>>> maintainers only send PULL requests for their queued patches after a
>>>>> couple of days. So relax, wait some days, and if your patch still did
>>>>> not get applied in a week, then you can start complaining again.
>>>>>
>>>>
>>>> i'll not complain again, i'm make a patch to clean my code from your
>>>> codebase.
>>>>
>>>
>>>
>>> Qemu have never been important to me like it's important to the
>>> maintainers.
>>>
>>>
>> i'm sure you can write your own AMD IOMMU.
>>
>
> in fact, i'll write the other patch then you can just choose what to merge.
>
> you're not as important as you try to pose.
>

and, by the way, i'm totally okay with Qemu guys stripping my code from
Qemu - that would be a lot better that a maintainer posing important to me
while maintaining code i wrote.

and, mind you, YOU ARE EMPLOYED. I WROTE THIS FOR FUN.


>
>
>>
>>
>>>
>>>
>>>>
>>>>
>>>>>
>>>>>  Thomas
>>>>>
>>>>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]