linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Zaytsev <alexey.zaytsev@gmail.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: Anderson Lizardo <anderson.lizardo@gmail.com>,
	linux-sparse@vger.kernel.org
Subject: Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs
Date: Mon, 1 Jun 2009 21:44:58 +0400	[thread overview]
Message-ID: <f19298770906011044o3affa20agc84787cfd9752618@mail.gmail.com> (raw)
In-Reply-To: <db65a1cd0906011036t6b83a97v38664b7d7ba06f51@mail.gmail.com>

On Mon, Jun 1, 2009 at 21:36, Samuel Bronson <naesten@gmail.com> wrote:
> On Mon, Jun 1, 2009 at 1:26 PM, Anderson Lizardo
> <anderson.lizardo@gmail.com> wrote:
>> On Mon, Jun 1, 2009 at 12:06 PM, Samuel Bronson <naesten@gmail.com> wrote:
>>> I just don't feel comfortable contributing under the OSL 1.1, for some
>>> reason -- possibly because it's considered non-DFSG, possibly because
>>> it's even more restrictive than the GPL ...
>>
>> If you look at the recent mailing list archives, you will find that a
>> particular snapshot of the git tree was relicensed by the original
>> copyright holder (Transmeta?) under the MIT license. It seems the
>> current developers intend to check with the other copyright holders
>> (for code commited after the particular relicensed snapshot) for a
>> license change.
>>
>> So I would you suggest at least using the MIT license to not "pollute"
>> the code with yet another license...
>
> Oh, sure, that's fine with me! Hadn't heard about that. The MIT/X11
> license is almost the same as the ISC license. Go ahead and s/ISC
> license/MIT license/ in these patches, though I don't think either of
> the patches that actually work (1/3 and 3/3) give me copyright on any
> code anyway.
>

Won't work that easily. Only an early sparse version, owned exclusively
by transmeta may be alternatively distribute under the MIT license. To
convert the current sparse version to MIT, we need to get all the
contributors to agree to this. Not impossible, but someone needs to
send lots of emails. ;)

  reply	other threads:[~2009-06-01 17:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31 15:44 [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs Samuel Bronson
2009-05-31 15:44 ` [PATCH 2/3] Replace SYM_ and MOD_ #defines with enums in symbol.h Samuel Bronson
2009-05-31 15:44   ` [PATCH 3/3] Whitespace tweaks " Samuel Bronson
2009-05-31 16:03   ` [PATCH 2/3] Replace SYM_ and MOD_ #defines with enums " Samuel Bronson
2009-06-01  6:21 ` [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs Alexey Zaytsev
2009-06-01 16:06   ` Samuel Bronson
2009-06-01 17:26     ` Anderson Lizardo
2009-06-01 17:36       ` Samuel Bronson
2009-06-01 17:44         ` Alexey Zaytsev [this message]
2009-06-01 17:50           ` Samuel Bronson
2009-06-01 17:26     ` Alexey Zaytsev

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=f19298770906011044o3affa20agc84787cfd9752618@mail.gmail.com \
    --to=alexey.zaytsev@gmail.com \
    --cc=anderson.lizardo@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=naesten@gmail.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 NNTP newsgroup(s).