From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Gustaf Waldemarson Newsgroups: gmane.emacs.bugs Subject: bug#34589: 26.1.91; GDB-MI Display Complex Data Types Date: Sun, 3 Mar 2019 21:32:46 +0100 Message-ID: References: <83wolugz2r.fsf@gnu.org> <83va1aq1ui.fsf@gnu.org> <83o972pz92.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="153156"; mail-complaints-to="usenet@blaine.gmane.org" Cc: rpluim@gmail.com, rms@gnu.org To: 34589@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Mar 03 21:37:07 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h0Xr9-000deK-Ap for geb-bug-gnu-emacs@m.gmane.org; Sun, 03 Mar 2019 21:37:07 +0100 Original-Received: from localhost ([127.0.0.1]:43926 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0Xr8-0006sh-0w for geb-bug-gnu-emacs@m.gmane.org; Sun, 03 Mar 2019 15:37:06 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:46169) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h0XoB-0004Ue-M2 for bug-gnu-emacs@gnu.org; Sun, 03 Mar 2019 15:34:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h0XoA-0006UN-HZ for bug-gnu-emacs@gnu.org; Sun, 03 Mar 2019 15:34:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45178) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h0XoA-0006U4-BY for bug-gnu-emacs@gnu.org; Sun, 03 Mar 2019 15:34:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h0XoA-00024e-7w for bug-gnu-emacs@gnu.org; Sun, 03 Mar 2019 15:34:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gustaf Waldemarson Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 03 Mar 2019 20:34:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34589 X-GNU-PR-Package: emacs Original-Received: via spool by 34589-submit@debbugs.gnu.org id=B34589.15516451867909 (code B ref 34589); Sun, 03 Mar 2019 20:34:02 +0000 Original-Received: (at 34589) by debbugs.gnu.org; 3 Mar 2019 20:33:06 +0000 Original-Received: from localhost ([127.0.0.1]:58722 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h0XnF-00023V-Ps for submit@debbugs.gnu.org; Sun, 03 Mar 2019 15:33:06 -0500 Original-Received: from mail-ed1-f66.google.com ([209.85.208.66]:41834) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h0XnD-00022d-VD for 34589@debbugs.gnu.org; Sun, 03 Mar 2019 15:33:04 -0500 Original-Received: by mail-ed1-f66.google.com with SMTP id x7so2564896eds.8 for <34589@debbugs.gnu.org>; Sun, 03 Mar 2019 12:33:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Wpt1YD6jbFsqIHWYDkYn4dIV14OmChJVBDbKW/BF5mM=; b=bBRlHC7mW3a8rVzN3klHp2eqGVwDHbZQw1lcg0SUWv5G6NB/uEN/1UcD3Xg4mr67DB gK0EMgNGinBL1OSre3WFeB893TSPH7JPfPHjktA2HvB9ofmXwmms4Zs7g39EgPffO6EN zLxyPhiRFAdpqHrL5g1BUxKQ/vv0/PMvBzawb1cxCi2DKaN+oCoCfVKVy/3DAHs+QQIj 7CPm9Tcej6TucmoXyRzcNlDMzkoTqyPl33kNubJF8WpxR45uf6TbDonFhfxd1kZheCpz oMlAT4QXZKf8g4LAFjwvIBVBHkB6KFg4WbYdvUFNtTqJOA/+l6fHMfbHZn490NmWZwXT VkeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Wpt1YD6jbFsqIHWYDkYn4dIV14OmChJVBDbKW/BF5mM=; b=UZoM0ZoXEJtuG07Ow+Yqq3wrNP/Qk6+AR1MExFTcmI9V/d8k3K3rn9JPsABFIb6i1e lfFg9kqi9GS13So7Q+u4CISj6beb47kHn/1GWVS93kg4sDvczFirzRsdYfSNkuvSYzKz SOeL+om91s5CKOTSA7I0ER333bdjPRBKcwRIxQo0roADwuwvKYs62Z0Cbivex3EZxWqi AwKnh6F3GAcswS8eMD5LeO+IoXqg7JoVCXOf6IkyODKkjEC8aQHCVxvg3MXswDVXQjor dlMkZEzusLTddtV0b3eyrPJ1L9RVvx8clhTAuJMMinkxS7pQd+gfpZ5HAhDHzO/2tJyr IupA== X-Gm-Message-State: APjAAAUcfEcJaUc1sBG66OsXIeZeimmtPLdZenTVgmuZlHqmcPNydM9+ BAdhBDOasQmT5vjfbBpDM7Q6SzvaA9mtzZtSatOhYZCt X-Google-Smtp-Source: APXvYqypqbWjFZ/ndpSDeaJpGBUIiPmLWsxk7oqCHAgzWbJD+R2j5FJlJxbOGLVA4cCXkFJZyxCKj+vQFG9SFE0TZQM= X-Received: by 2002:a50:f5ea:: with SMTP id x39mr12806404edm.154.1551645177463; Sun, 03 Mar 2019 12:32:57 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:156009 Archived-At: > May be narrowing to very specific area (emacs, gdb-mi, no-arm-specific) w= ould > help? It seems like that could be a possibility. I did get a bit more "willing" m= ail last Friday evening but I suspect will require quite a bit more time from everyone involved. I'll keep track of things internally, but for now I beli= eve we should consider the patches unusable. > Does the first patch have value on its own? If so, we can accept it witho= ut > legal paperwork. I would argue that either patch have some value. The first patch enables di= splay of the complex data types and the second changes the interface to use a non-deprecated function from the gdb interface that additionally lists func= tion arguments as well, something the previous one did not (at least if I have understood the documentation correctly). Although, the first patch in my list is the bigger one. Wasn't that part of= the problem legal-wise? > If you think you have a chance of findin another job, you might want to l= ook > for one, negotiating for a suitable copyright disclaimer about contributi= ons > to free software as part of your employment contract itself. Do ask your > lawyer (NOT the company's lawyer) to check it. I'm afraid I'm not in a position in life where this is something that I can consider. Although, I will keep it in mind in the future. > It=CA=BCs doubly surprising, given that Arm employees contribute patches = to > binutils all the time. >From what I've been told (and this might very well be third-hand info or wo= rse), Arm employees working on binutils and GCC can do so under an older agreemen= t that was in place prior to the introduction of the employer disclaimer. They also told me that *if* Emacs was covered by that agreement, the patche= s could be used given that they were re-authored to use my Arm e-mail, but I'= ve not heard back from them regarding that. > Depending on what country you=CA=BCre in, your employer may have no claim > whatsoever on code that you come up with on your own time (sometimes > even if you came up with it *during* your actual work for them). > > Of course, this is a complex area, so you'd need to consult a lawyer > to be sure (and I=CA=BCm not one :-) ) Funny that you would mention that. I've heard similar things elsewhere, but unfortunately I'm not in a position where I can challenge Arm regarding thi= s to change my contract. As I mentioned earlier though, I will be more careful t= he future. > So you could respond by demanding they tell you concretely what kind of t= hing > they are talking about "exposing", instead of giving you a mysifying answ= er. Thanks, I'll be sure to do just that. Den l=C3=B6r 2 mars 2019 kl 04:28 skrev Richard Stallman : > > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > > Apparently Arm has taken the > > stance that signing such a disclaimer could "open a legal door which > > could expose intellectual property in the future". > > The term "intellectual property" is a tool for mystification. > It spreads confusion every time it is used, and that is why they use it. > See https://gnu.org/philosophy/not-ipr.html. > > It takes an overgeneralization -- "intellecual property law" -- which > should never be used -- and then reifies it. > > So you could respond by demanding they tell you concretely what kind > of thing they are talking about "exposing", instead of giving you > a mysifying answer. > > -- > Dr Richard Stallman > President, Free Software Foundation (https://gnu.org, https://fsf.org) > Internet Hall-of-Famer (https://internethalloffame.org) > >