From: "Carlos Martín Nieto" <cmn@dwim.me>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Christian Couder" <christian.couder@gmail.com>,
git <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Stefan Beller" <sbeller@google.com>,
"Jonathan Tan" <jonathantanmy@google.com>,
ethomson@edwardthomson.com, ps@pks.im
Subject: Re: Implementing reftable in Git
Date: Wed, 09 May 2018 20:05:41 +0200 [thread overview]
Message-ID: <e6f23463b1bd577d1c70848b11a0fd217b78f8a8.camel@dwim.me> (raw)
In-Reply-To: <20180509175445.GK10348@aiede.svl.corp.google.com>
On Wed, 2018-05-09 at 10:54 -0700, Jonathan Nieder wrote:
> Carlos Martín Nieto wrote:
> > On Wed, 2018-05-09 at 09:48 -0700, Jonathan Nieder wrote:
> > > If you would like the patches at https://git.eclipse.org/r/q/topi
> > > c:reftable
> > > relicensed for Git's use so that you don't need to include that
> > > license header, let me know. Separate from any legal concerns,
> > > if
> > > you're doing a straight port, a one-line comment crediting the
> > > JGit
> > > project would still be appreciated, of course.
>
> [...]
> > Would you expect that this port would keep the Eclipse Distribution
> > License or would it get relicensed to GPLv2?
>
> I think you're way overcomplicating things.
>
> The patches are copyright Google. We can handle issues as they come.
Fair enough. I just wanted to avoid coming back to this in a few months
and realising we can't use it at all.
Cheers,
cmn
next prev parent reply other threads:[~2018-05-09 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 14:33 Implementing reftable in Git Christian Couder
2018-05-09 14:52 ` Derrick Stolee
2018-05-09 16:07 ` Duy Nguyen
2018-05-09 16:48 ` Jonathan Nieder
2018-05-09 17:51 ` Carlos Martín Nieto
2018-05-09 17:54 ` Jonathan Nieder
2018-05-09 18:05 ` Carlos Martín Nieto [this message]
2018-05-09 17:42 ` Stefan Beller
2018-05-09 17:48 ` Jonathan Nieder
2018-05-09 17:55 ` Stefan Beller
2018-05-09 18:52 ` Ævar Arnfjörð Bjarmason
2018-05-11 9:31 ` Michael Haggerty
2018-05-11 22:21 ` David Turner
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=e6f23463b1bd577d1c70848b11a0fd217b78f8a8.camel@dwim.me \
--to=cmn@dwim.me \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=ethomson@edwardthomson.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=ps@pks.im \
--cc=sbeller@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.