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: 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:26:37 +0400	[thread overview]
Message-ID: <f19298770906011026k78143216u3384d36b3cdc7e7a@mail.gmail.com> (raw)
In-Reply-To: <db65a1cd0906010906x5e3b0044j181159e627b80800@mail.gmail.com>

On Mon, Jun 1, 2009 at 20:06, Samuel Bronson <naesten@gmail.com> wrote:
> On Mon, Jun 1, 2009 at 2:21 AM, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>> On Sun, May 31, 2009 at 19:44, Samuel Bronson <naesten@gmail.com> wrote:
>>> Changes-licensed-under: ISC license
>>
>> I don't think it works that way.
>
> Yeah, yeah, well it's a simple permissive license, so even if the
> patch introduced anything copyrightable -- which it presumably doesn't
> -- you could use it anyway.
>
> 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 ...
>

I'm not your lawyer, and not the sparse maintainer, but I strongly suspect
that that means that you can't contribute to sparse. And I'm not sure if you
could distribute the patches you sent at all, since they are derivative work,
and should be covered with the same license as sparse itself.

  c) to distribute copies of the Original Work and Derivative Works to
     the public, with the proviso that copies of Original Work or
     Derivative Works that You distribute shall be licensed under the
     Open Software License;

      parent reply	other threads:[~2009-06-01 17:26 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
2009-06-01 17:50           ` Samuel Bronson
2009-06-01 17:26     ` Alexey Zaytsev [this message]

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=f19298770906011026k78143216u3384d36b3cdc7e7a@mail.gmail.com \
    --to=alexey.zaytsev@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).