From: David Daney <ddaney@caviumnetworks.com>
To: "Ardelean, Andrei" <Andrei.Ardelean@idt.com>
Cc: linux-mips@linux-mips.org
Subject: Re: License file header for a new file
Date: Tue, 28 Sep 2010 09:50:14 -0700 [thread overview]
Message-ID: <4CA21CC6.9050101@caviumnetworks.com> (raw)
In-Reply-To: <AEA634773855ED4CAD999FBB1A66D0760115A22F@CORPEXCH1.na.ads.idt.com>
On 09/28/2010 07:40 AM, Ardelean, Andrei wrote:
> Hi,
>
> I am porting MIPS Linux from Malta to a new platform. I created a new
> file gd-memory.c from the original malta-memory.c and I modified the
> code to match the new platform. The original malta-memory.c has the
> following header:
> /*
> * Carsten Langgaard, carstenl@mips.com
> * Copyright (C) 1999,2000 MIPS Technologies, Inc. All rights reserved.
> *
> * This program is free software; you can distribute it and/or modify
> it
> * under the terms of the GNU General Public License (Version 2) as
> * published by the Free Software Foundation.
> *
> * This program is distributed in the hope it will be useful, but
> WITHOUT
> * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
> or
> * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
> License
> * for more details.
> *
> * You should have received a copy of the GNU General Public License
> along
> * with this program; if not, write to the Free Software Foundation,
> Inc.,
> * 59 Temple Place - Suite 330, Boston MA 02111-1307, USA.
> *
> * PROM library functions for acquiring/using memory descriptors given
> to
> * us from the YAMON.
> */
>
> What should be the correct header for gd-memory.c?
>
If there is code from the original file remaining, you should keep the
original copyright message
If you made material changes to it, you could *add* your own copyright line.
David Daney
prev parent reply other threads:[~2010-09-28 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:40 License file header for a new file Ardelean, Andrei
2010-09-28 14:40 ` Ardelean, Andrei
2010-09-28 16:50 ` David Daney [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=4CA21CC6.9050101@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=Andrei.Ardelean@idt.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox