git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Han-Wen Nienhuys <hanwen@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git <git@vger.kernel.org>, Christian Couder <christian.couder@gmail.com>
Subject: Re: Reftable format implementation in C and Go
Date: Wed, 20 Nov 2019 06:22:10 -0800	[thread overview]
Message-ID: <CAFQ2z_PBPPQuJYA-mvKz532GikBXureOi1ePr7YdBRJbxOJCeA@mail.gmail.com> (raw)
In-Reply-To: <CAFQ2z_PiuFe=ZKNaZG3=2AqjcNRb-k5-CYSXeN6MQ0r5sv4S=g@mail.gmail.com>

On Wed, Nov 20, 2019 at 6:19 AM Han-Wen Nienhuys <hanwen@google.com> wrote:
>> Would you mind, however, to relicense the code under a license compatible
>> with GPLv2? Currently your code is under the Apache License (which I heard
>> somewhere is probably incompatible with the GPLv2 used by the Git
>> project):
>> https://github.com/google/reftable/blob/6cd8dbb4106d18627f442d3148de71d7db43d4b6/c/api.h#L1-L13
>>

according to our open source lawyers, Apache is actually compatible
with GPLv2, but I think we could dual-license the code.


-- 
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

  parent reply	other threads:[~2019-11-20 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFQ2z_Pe1Pdjy22VmCMzf4Gvx3wte1eQRn_PjSisJbr9_y7bbg@mail.gmail.com>
2019-11-20 11:48 ` Reftable format implementation in C and Go Johannes Schindelin
     [not found]   ` <CAFQ2z_PiuFe=ZKNaZG3=2AqjcNRb-k5-CYSXeN6MQ0r5sv4S=g@mail.gmail.com>
2019-11-20 14:22     ` Han-Wen Nienhuys [this message]
2019-11-20 14:34       ` Pratyush Yadav

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFQ2z_PBPPQuJYA-mvKz532GikBXureOi1ePr7YdBRJbxOJCeA@mail.gmail.com \
    --to=hanwen@google.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).