public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new board with i.MX31 processor
Date: Wed, 09 Jul 2008 08:09:10 -0400	[thread overview]
Message-ID: <4874AA66.1010500@ge.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807090048470.30894@axis700.grange>

Guennadi Liakhovetski wrote:
> On Tue, 8 Jul 2008, Jens Gehrlein wrote:
> 
>> diff --git a/board/tqc/tqma31/Makefile b/board/tqc/tqma31/Makefile
>> new file mode 100644
>> index 0000000..f7e17c8
>> --- /dev/null
>> +++ b/board/tqc/tqma31/Makefile
>> @@ -0,0 +1,48 @@
>> +#
>> +# Copyright (C) 2008, Guennadi Liakhovetski <lg@denx.de>
>> +# Copyright (C) 2008, Jens Gehrlein <sew_s@tqs.de>
> 
> Thanks for the credit, but, although IANAL, I think, one does not _have_ 
> to preserve the copyright of the original file when it gets copied to a 
> new one. Otherwise most open-source files would have a veeeery long list 
> of Copyrights:-) Am I right?
> 
> Thanks
> Guennadi

IANAL, but I play one on Groklaw sometimes, much to PJ's chagrin. ;-)

This is a squishy area.  It is dependent on what of the original work 
survives the modification and whether the surviving pieces are 
copyrightable.  It also depends on what country you are contemplating 
suing in.

<http://en.wikipedia.org/wiki/Limitations_and_exceptions_to_copyright>

Things that must be done in certain ways are not copyrightable, so 
Makefiles are pretty marginal to start with IMHO.

<http://en.wikipedia.org/wiki/Threshold_of_originality>

My opinion is to leave the original copyright notice in there and err on 
the side of preserving reasonable copyright notices.  The lawyers will 
be happy to tell us that we did it wrong if it ever came to a lawsuit, 
and I would prefer that they tell us that we had a useless copyright 
notice in the file rather than tell us that we should have had a notice 
but didn't...

Best regards,
gvb

  parent reply	other threads:[~2008-07-09 12:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08  9:33 [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new board with i.MX31 processor Jens Gehrlein
2008-07-08 10:32 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-08 12:09   ` Jens Gehrlein
2008-07-08 15:24     ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-08 14:31 ` Wolfgang Denk
2008-07-08 15:14   ` Jens Gehrlein
2008-07-09 22:46     ` Wolfgang Denk
2008-07-10  6:22       ` Jens Gehrlein
2008-07-10  6:55         ` Wolfgang Denk
2008-07-10  7:29           ` [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new boardwith " Martin Krause
2008-07-10 20:54         ` [U-Boot-Users] [PATCH 04/10 v2] [ARM] TQMA31: add new board with " Guennadi Liakhovetski
2008-07-10  8:20       ` Sascha Hauer
2008-07-10  8:17     ` Sascha Hauer
2008-07-10  8:49       ` Wolfgang Denk
2008-07-10  9:30         ` Sascha Hauer
2008-07-10  9:46           ` Wolfgang Denk
2008-07-10 10:16             ` Sascha Hauer
2008-07-08 22:55 ` Guennadi Liakhovetski
2008-07-08 23:16   ` Wolfgang Denk
2008-07-08 23:33     ` Guennadi Liakhovetski
2008-07-09  6:50       ` Wolfgang Denk
2008-07-09  6:32   ` Jens Gehrlein
2008-07-09  7:10     ` Wolfgang Denk
2008-07-09 12:09   ` Jerry Van Baren [this message]
     [not found] <mailman.707077.1215511129.5026.u-boot-users@lists.sourceforge.net>
2008-07-08 11:33 ` Heiko Schocher
2008-07-08 11:38   ` Jens Gehrlein
2008-07-08 13:48     ` Heiko Schocher

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=4874AA66.1010500@ge.com \
    --to=gerald.vanbaren@ge.com \
    --cc=u-boot@lists.denx.de \
    /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