All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Patches have a license
Date: Mon, 27 Jan 2003 12:47:29 +0100	[thread overview]
Message-ID: <3E351C51.FAF985BC@aitel.hist.no> (raw)
In-Reply-To: 20030127104705.GC25913@codemonkey.org.uk

Dave Jones wrote:
> 
> On Mon, Jan 27, 2003 at 01:58:40AM -0800, Balbir Singh wrote:
>  > I would request everyone to post their patches with
>  > a license, failing which it should be assumed that
>  > the license is GPL.
> 
> Surely the license of the diff matches the license of the
> code it is patching ?

Usually in practice, but not necessarily.  Try diff'ing
two files with different licence, then go apply
it at some file with a third licence. :-/

Helge Hafting

  parent reply	other threads:[~2003-01-27 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27  9:58 [RFC] Patches have a license Balbir Singh
2003-01-27 10:47 ` Dave Jones
2003-01-27 11:10   ` John Bradford
2003-01-27 11:30   ` Andre Hedrick
2003-01-27 11:34   ` Sean Neakums
2003-01-27 11:47   ` Helge Hafting [this message]
2003-01-27 20:04   ` dean gaudet
2003-01-27 12:03 ` Russell King
2003-01-27 12:12   ` Andre Hedrick

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=3E351C51.FAF985BC@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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.