qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [GitHub] [Qemu-commits] [qemu/qemu] ecdffb: tcg/ppc: Re


From: Anthony Liguori
Subject: Re: [Qemu-devel] [GitHub] [Qemu-commits] [qemu/qemu] ecdffb: tcg/ppc: Remove unused s_bits variable
Date: Fri, 30 Nov 2012 09:43:29 -0600
User-agent: Notmuch/0.13.2+93~ged93d79 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu)

I've spent the past week thinking about what to do here.  Honestly, I'm
tired of this nonsense.  Every few months there's another headache to
deal with.

So I'm going to make it simple.  You do *not* commit patches to the git
tree without sending them to the list first to review.  You do *not*
relicense files without getting approval from every single contributor
to that file.

I don't care about whether changes are trivial and I don't want to hear
pseudo-legal arguments about copyright-ability.  This is about basic
decency and respect for the other members of this community.

Commit access is a privilege, not a right.  If you can't abide by the
basic rules of the community, then you'll lose that privilege.

I've reverted these two commits.  If you want to relicense these files,
send patches to the mailing list and get the appropriate Acks.

I'm done with the drama though.  This is the last time this is going to
happen one way or another.

Regards,

Anthony Liguori

malc <address@hidden> writes:

> On Tue, 20 Nov 2012, Anthony Liguori wrote:
>
>> malc <address@hidden> writes:
>
> [..snip..]
>
>> Hi malc,
>> 
>> If you want to put code under the public domain, it needs to be done (1)
>> with the consent of all contributors to a file (2) using an appropriate
>> license.
>> 
>> In QEMU, we've always followed the FSF's guidance when it comes to
>> licensing issues.  
>
> Uh... I doubt it having been here for a while.
>
>> This isn't something that's up for discussion.
>
> And i'm not discussing it.
>
>> Please revert the change, send a patch with an appropriate license, and
>> get the contributors to Ack the change.
>
> No, i'm the sole author of audio_pt_int.c, and i've chosen to put it into
> public domain, the notice is sufficient to indicate my desire.
>
> As for wavcapture.c the changes by others (yourself included) boil down to
> mechanical renaming of some function calls, i'd rather revert that and redo
> it myself (or ask someone to do it) if "we" are feeling strongly about it.
>
> FWIW [winwave|pa]audio.c had the same comment since inception and in case
> of paaudio.c Marc-Andrц╘ Lureau's basically redid the interaction with pa
> but left the header intact.
>
> aes.c says: This code is hereby placed in the public domain.
>       Followed by some legalese to disclaim warranties.
>
> d3des.c: A portable, public domain, version of the Data Encryption Standard.
>       Followed by Copyright (c) 1988,1989,1990,1991,1992 by Richard 
> Outerbridge.
>       which i do not follow since either thing is in public domain or has
>       some copy restrictions.
>
> In any case this all is bordering insanity, what next? Follow FSF even
> closer and demand everything to be GPL and faxing hand signed
> ownership transfer papers somewhere?
>
> -- 
> mailto:address@hidden



reply via email to

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