All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <junio@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2010, #06; Tue, 23)
Date: Wed, 24 Feb 2010 01:28:51 -0500	[thread overview]
Message-ID: <20100224062850.GA12796@coredump.intra.peff.net> (raw)
In-Reply-To: <7v635nsa37.fsf@alter.siamese.dyndns.org>

On Tue, Feb 23, 2010 at 05:20:44PM -0800, Junio C Hamano wrote:

> * cw/test-lib-relicense (2010-02-22) 1 commit
>  . test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.
> 
> I think a reasonable way forward would be to collect Acks from
> everybody who appears on "git blame" or "git shortlog" output.

Somehow I am number 4 on "git shortlog -ns" for test-lib.sh, despite
having contributed only a tiny number of lines. :)  But certainly I am
fine with re-licensing it.

> How do people feel about relicensing the whole (except for the
> obviously borrowed bits, such as xdiff/) under GPLv2 _or later_?  I am
> not a big fan of GPLv3 and do not see a compelling reason to switch to
> v3 for the sake of v3 license per-se, but helping others that want to
> use our code might tip the balance.

I have no problem with re-licensing my contributions.

-Peff

  parent reply	other threads:[~2010-02-24  6:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  1:20 What's cooking in git.git (Feb 2010, #06; Tue, 23) Junio C Hamano
2010-02-24  2:06 ` Tay Ray Chuan
2010-02-24  6:28 ` Jeff King [this message]
2010-02-24 15:09 ` Nicolas Pitre
2010-02-24 23:42   ` Junio C Hamano
2010-02-25  0:11     ` Nelson Elhage
2010-02-25 21:39 ` Sverre Rabbelier

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=20100224062850.GA12796@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=junio@pobox.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.