From: Eli Zaretskii <eliz@gnu.org>
To: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
Cc: 34589@debbugs.gnu.org
Subject: bug#34589: 26.1.91; GDB-MI Display Complex Data Types
Date: Thu, 28 Feb 2019 19:58:21 +0200 [thread overview]
Message-ID: <83fts7kd6q.fsf@gnu.org> (raw)
In-Reply-To: <CABehr5f332Fca7kxbJw9QSwYWP352=CU13=RiH9vLHCdKHWGUA@mail.gmail.com> (message from Gustaf Waldemarson on Thu, 28 Feb 2019 17:05:35 +0100)
> From: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
> Date: Thu, 28 Feb 2019 17:05:35 +0100
> Cc: 34589@debbugs.gnu.org
>
> I'm afraid I have some bad news regarding the patches. As I was
> looking for someone internally at Arm to sign the employer disclaimer
> I was stopped by the legal department. Apparently Arm has taken the
> stance that signing such a disclaimer could "open a legal door which
> could expose intellectual property in the future". Thus, I'm afraid no
> one at Arm will sign such a disclaimer at this time and consequently,
> these patches cannot be used in Emacs.
>
> I'm not exactly a lawyer, but I believe the patches can still be used
> as a reference for implementing the feature, but as I mentioned I'm
> afraid they cannot be used as-is.
>
> Sorry about the trouble, I didn't really expect the company to stop
> something like this.
Sorry to hear that.
Does the first patch have value on its own? If so, we can accept it
without legal paperwork.
Thanks.
next prev parent reply other threads:[~2019-02-28 17:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 10:08 bug#34589: 26.1.91; GDB-MI Display Complex Data Types Gustaf Waldemarson
2019-02-20 17:16 ` Eli Zaretskii
2019-02-21 13:42 ` Gustaf Waldemarson
2019-02-23 9:40 ` Eli Zaretskii
2019-02-23 10:01 ` Gustaf Waldemarson
2019-02-23 10:36 ` Eli Zaretskii
2019-02-28 16:05 ` Gustaf Waldemarson
2019-02-28 17:24 ` Andrew W. Nosenko
2019-02-28 17:58 ` Eli Zaretskii [this message]
2019-03-01 3:57 ` Richard Stallman
2019-03-02 3:28 ` Richard Stallman
2019-03-03 20:32 ` Gustaf Waldemarson
2019-03-04 3:30 ` Eli Zaretskii
2019-03-04 8:05 ` Gustaf Waldemarson
2019-03-08 9:06 ` Eli Zaretskii
2019-11-05 10:05 ` Gustaf Waldemarson
2020-09-30 18:08 ` Lars Ingebrigtsen
2020-09-30 18:30 ` Eli Zaretskii
2020-04-15 14:54 ` Yuan Fu
2020-04-15 15:05 ` Eli Zaretskii
2022-03-06 20:39 ` William Xu
2022-03-06 20:44 ` William Xu
2022-03-06 20:46 ` Weilin Xu
2022-03-06 21:56 ` Lars Ingebrigtsen
2022-03-06 22:33 ` William Xu
2022-03-06 23:02 ` Lars Ingebrigtsen
2022-03-07 9:27 ` William Xu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fts7kd6q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34589@debbugs.gnu.org \
--cc=gustaf.waldemarson@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).