From: Dodji Seketeli <dodji@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Benjamin Kosnik <b.dekosnik@gmail.com>,
Ben Woodard <woodard@redhat.com>, Chenxiong Qi <cqi@redhat.com>,
Giuliano Procida <gprocida@google.com>,
Jan Engelhardt <jengelh@inai.de>, Jessica Yu <jeyu@kernel.org>,
Jonathan Wakely <jwakely@redhat.com>,
Matthias Klose <doko@debian.org>,
Matthias Maennich <maennich@google.com>,
Ondrej Oprala <ondrej.oprala@gmail.com>,
Roland McGrath <roland@hack.frob.com>,
Sinny Kumari <skumari@redhat.com>,
Slava Barinov <v.barinov@samsung.com>,
libabigail@sourceware.org
Subject: Re: [PATCH 0/9] Relicensing Libabigail to Apache 2.0 + LLVM Exception
Date: Mon, 13 Jul 2020 13:45:17 +0200 [thread overview]
Message-ID: <86sgdvvdte.fsf@redhat.com> (raw)
In-Reply-To: <20200710145857.GB61524@wildebeest.org> (Mark Wielaard's message of "Fri, 10 Jul 2020 16:58:57 +0200")
Hello Mark,
Mark Wielaard <mark@klomp.org> writes:
> Hi Dodji,
>
> On Fri, Jul 10, 2020 at 04:05:20PM +0200, Dodji Seketeli via Libabigail wrote:
>> This patch series is to relicense the source code of the Libabigail
>> project to Apache 2.0 with LLVM Exception.
>>
>> The rationale and the process of this change was recently presented in
>> a message sent to the mailing list of the project at
>> https://sourceware.org/pipermail/libabigail/2020q2/002388.html.
>>
>> This patch series needs to be reviewed and acknowledged by all the
>> copyright holders who contributed to the project. These contributors
>> are all listed in the "To:" field of this message.
>
> As I said earlier I think dropping all copyleft is the wrong move for
> the project. And personally I feel this is very demotivating for
> contributing in the future.
I understand and respect your point of view ...
> But if you believe a majority of the contributors agrees with this
> change then I won't block it.
... and I therefore value and greatly appreciate this balanced stance of
yours. Thank you for that.
> So, if you do get a majority of the contributors to add their
> Signed-of-by for the patches, then feel free to also add my
> Signed-off-by.
Thanks.
Cheers,
--
Dodji
next prev parent reply other threads:[~2020-07-13 11:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 14:05 Dodji Seketeli
2020-07-10 14:58 ` Mark Wielaard
2020-07-13 11:45 ` Dodji Seketeli [this message]
2020-12-02 11:07 ` Relicensing Signed-off-by from Mark Wielaard Dodji Seketeli
2020-07-10 15:28 ` [PATCH 0/9] Relicensing Libabigail to Apache 2.0 + LLVM Exception Matthias Maennich
2020-07-13 11:42 ` Dodji Seketeli
2020-07-15 14:26 ` Matthias Klose
2020-07-16 9:47 ` Dodji Seketeli
[not found] ` <8A94C8B5-A9DF-4E03-B088-552061A95A8F@redhat.com>
2020-07-24 8:19 ` Dodji Seketeli
2020-09-09 20:43 ` Roland McGrath
2020-09-10 9:23 ` Dodji Seketeli
2020-09-23 16:07 ` Benjamin De Kosnik
2020-09-23 21:54 ` Ondrej Oprala
2020-09-24 9:12 ` Dodji Seketeli
2020-09-24 9:11 ` Dodji Seketeli
2020-10-20 13:36 ` Sinny Kumari
2020-12-02 10:42 ` Dodji Seketeli
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=86sgdvvdte.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=b.dekosnik@gmail.com \
--cc=cqi@redhat.com \
--cc=doko@debian.org \
--cc=gprocida@google.com \
--cc=jengelh@inai.de \
--cc=jeyu@kernel.org \
--cc=jwakely@redhat.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
--cc=mark@klomp.org \
--cc=ondrej.oprala@gmail.com \
--cc=roland@hack.frob.com \
--cc=skumari@redhat.com \
--cc=v.barinov@samsung.com \
--cc=woodard@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 read-only IMAP folder(s) and NNTP newsgroup(s).