delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/04/04/21:59:14

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 4 Apr 2005 21:58:47 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: zsh startup oddity
Message-ID: <20050405015847.GA15452@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <1112600771 DOT 24256 DOT 5 DOT camel AT localhost DOT localdomain> <20050404235407 DOT B816C8553D AT pessard DOT research DOT canon DOT com DOT au>
Mime-Version: 1.0
In-Reply-To: <20050404235407.B816C8553D@pessard.research.canon.com.au>
User-Agent: Mutt/1.5.8i

On Tue, Apr 05, 2005 at 09:54:07AM +1000, Luke Kendall wrote:
>On  4 Apr, Michael Wardle replied to:
>>  > BTW, should you include a copyright and license term comment in shell.c? 
>>  > It would make me feel much more comfortable. 
>>   
>>  It's a trivial program I wrote with reference to no other programs.  I 
>>  hereby release it into the public domain.  Use it as you like. 
>
>Great, but for legal reasons, doesn't that statement need to be inside
>the source file itself?  I thought you'd need to have a copyright
>statement in there so that it even had a *chance* of being adopted into
>the official Cygwin release.
>
>I had a look at http://cygwin.com/contrib.html, and saw these
>guidelines:
>
>    If your change is going to be a significant one in terms of
>    the size of your code changes, be aware that you will have to
>    sign over the copyright ownership of your code changes to Red
>    Hat or the FSF (depending on the source file) before we can
>    include your changes in the main source tree. Your employer may
>    also have to send us a disclaimer stating that they have no
>    claims to your contribution. This is necessary for liability
>    reasons. Here [http://cygwin.com/assign.txt] is our standard
>    assignment form for changes to Cygwin that you can fill out, sign,
>    and send back.

The web page that you are referring to has this at the beginningr:

    This document deals with contributions to the Cygwin DLL and Cygwin
    utilitites.  Contributions to other packages contributed by Cygwin are
    also welcome and some of the principles involved are the same.
    However, most of the specific instructions here will not be applicable
    to utilities like bash, gawk, apache, etc., which are generally found
    in linux releases.  If you have a patch for any of those, send it along
    to the cygwin mailing list and the appropriate package maintainer will
    respond.

i.e., it has nothing to do with any of the non-cygwin-specific packages
so it is not applicable here.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019