From: Maxim Grigoriev <maxim@tensilica.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] CHANGES: add #163 + #473
Date: Fri, 24 Jul 2009 10:29:46 -0700 [thread overview]
Message-ID: <4A69EF8A.5080802@tensilica.com> (raw)
In-Reply-To: <20090724153528.7103ad9d@surf>
I'm concerned by the licensing of
target/xtensa/xt-buildroot-overlay-install, since this file states:
+# Copyright (c) 2003-2008 by Tensilica Inc. ALL RIGHTS RESERVED.
+# These coded instructions, statements, and computer programs are the
+# copyrighted works and confidential proprietary information of Tensilica Inc.
+# They may not be modified, copied, reproduced, distributed, or disclosed to
+# third parties in any manner, medium, or form, in whole or in part, without
+# the prior written consent of Tensilica Inc.
This one has to be fixed, of course.
If you can, please, simply remove the copyright I'd really appreciate it.
I don't hove a write-access to Buildroot.
-- Maxim
Thomas Petazzoni wrote:
> Le Fri, 24 Jul 2009 15:02:42 +0200,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>
>
>> Yes, they are committed and I haven't seen the mails either - seems
>> like the commit hook has issues when I push multiple changes at once.
>>
>> (Or it might be something else, I'm having mail and hw problems
>> today).
>>
>
> I haven't seen the mails either. So not likely to be a problem on your
> side.
>
>
>> I agree that the xtensa stuff is "special" in various ways, but I
>> think it's more productive to get it into git and then work on getting
>> it cleaned up more, instead of having it gather dust in bugzilla.
>>
>
> Ok, fair enough. Reading the patches again, they don't look too
> invasive after all.
>
> I'm concerned by the licensing of
> target/xtensa/xt-buildroot-overlay-install, since this file states:
>
> +# Copyright (c) 2003-2008 by Tensilica Inc. ALL RIGHTS RESERVED.
> +# These coded instructions, statements, and computer programs are the
> +# copyrighted works and confidential proprietary information of Tensilica Inc.
> +# They may not be modified, copied, reproduced, distributed, or disclosed to
> +# third parties in any manner, medium, or form, in whole or in part, without
> +# the prior written consent of Tensilica Inc.
>
> BTW, was Perl already a host dependency to run Buildroot ?
>
> Sincerly,
>
> Thomas
>
next prev parent reply other threads:[~2009-07-24 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 5:51 [Buildroot] [git commit] CHANGES: add #163 + #473 Peter Korsgaard
2009-07-24 9:02 ` Thomas Petazzoni
2009-07-24 13:02 ` Peter Korsgaard
2009-07-24 13:35 ` Thomas Petazzoni
2009-07-24 13:46 ` Gustavo Zacarias
2009-07-24 13:52 ` Peter Korsgaard
2009-07-24 13:50 ` Peter Korsgaard
2009-07-24 17:31 ` Maxim Grigoriev
2009-07-24 13:51 ` Marc Gauthier
2009-07-24 13:56 ` Peter Korsgaard
2009-07-24 18:21 ` Maxim Grigoriev
2009-07-25 6:41 ` Peter Korsgaard
2009-07-24 17:29 ` Maxim Grigoriev [this message]
2009-07-24 21:54 ` Thomas Petazzoni
2009-07-25 3:22 ` Maxim Grigoriev
2009-07-28 1:48 ` Maxim Grigoriev
2009-07-28 17:42 ` Marc Gauthier
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=4A69EF8A.5080802@tensilica.com \
--to=maxim@tensilica.com \
--cc=buildroot@busybox.net \
/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