From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexey Zaytsev Subject: Re: [PATCH 1/3] Add -*- gdb-script -*- to the top of gdbhelpers, for Emacs Date: Mon, 1 Jun 2009 21:26:37 +0400 Message-ID: References: <1243784652-31802-1-git-send-email-naesten@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-fx0-f168.google.com ([209.85.220.168]:50311 "EHLO mail-fx0-f168.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751670AbZFAR0h (ORCPT ); Mon, 1 Jun 2009 13:26:37 -0400 Received: by fxm12 with SMTP id 12so5939690fxm.37 for ; Mon, 01 Jun 2009 10:26:37 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Samuel Bronson Cc: linux-sparse@vger.kernel.org On Mon, Jun 1, 2009 at 20:06, Samuel Bronson wrote: > On Mon, Jun 1, 2009 at 2:21 AM, Alexey Zaytsev wrote: >> On Sun, May 31, 2009 at 19:44, Samuel Bronson 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;