From: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, 34589@debbugs.gnu.org, rms@gnu.org
Subject: bug#34589: 26.1.91; GDB-MI Display Complex Data Types
Date: Mon, 4 Mar 2019 09:05:26 +0100 [thread overview]
Message-ID: <CABehr5fY_-irLDUgyfrN2XOwESdS6YJ5rsZFw19pEJOizCLAEA@mail.gmail.com> (raw)
In-Reply-To: <83zhqbe2og.fsf@gnu.org>
>Yes. I asked about the first patch because it's small enough to be
> accepted even without legal paperwork. The second one exceeds the
> limits of that.
Ah, got it. Feel free to review and include it if you find it useful.
If Arm ever get back
to me regarding the legal stuff I'll submit them then as a separate bug.
Den mån 4 mars 2019 kl 04:31 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > From: Gustaf Waldemarson <gustaf.waldemarson@gmail.com>
> > Date: Sun, 3 Mar 2019 21:32:46 +0100
> > Cc: Eli Zaretskii <eliz@gnu.org>, andrew.w.nosenko@gmail.com, rpluim@gmail.com, rms@gnu.org
> >
> > > Does the first patch have value on its own? If so, we can accept it without
> > > legal paperwork.
> >
> > I would argue that either patch have some value. The first patch enables display
> > of the complex data types and the second changes the interface to use a
> > non-deprecated function from the gdb interface that additionally lists function
> > 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?
>
> Yes. I asked about the first patch because it's small enough to be
> accepted even without legal paperwork. The second one exceeds the
> limits of that.
>
next prev parent reply other threads:[~2019-03-04 8:05 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
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 [this message]
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=CABehr5fY_-irLDUgyfrN2XOwESdS6YJ5rsZFw19pEJOizCLAEA@mail.gmail.com \
--to=gustaf.waldemarson@gmail.com \
--cc=34589@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@gnu.org \
--cc=rpluim@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).