unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: gustaf.waldemarson@gmail.com, 34589@debbugs.gnu.org
Subject: bug#34589: 26.1.91; GDB-MI Display Complex Data Types
Date: Wed, 30 Sep 2020 21:30:40 +0300	[thread overview]
Message-ID: <837dsbi0bz.fsf@gnu.org> (raw)
In-Reply-To: <87v9fvyw6f.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  30 Sep 2020 20:08:24 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 30 Sep 2020 20:08:24 +0200
> Cc: 34589@debbugs.gnu.org
> 
> Gustaf Waldemarson <gustaf.waldemarson@gmail.com> writes:
> 
> > After quite some time here, I have finally been able to get the proper
> > legal confirmation from Arm to submit patches. As far as I understand
> > things, any patch that I submit for Emacs will now have the copyright
> > correctly reassigned and should now be usable without any issues.
> 
> Great!  Your patch didn't apply cleanly to Emacs 28, so I've respun it
> (included below).
> 
> There was unfortunately no followup on this at the time, and I'm not
> exactly a gdb expert (cough cough).

This is a new feature, so it can only break itself, no?

> Could somebody give this a look-over?  It looks good to me, but I
> haven't tested it.

If the OP could propose a simple sequence of commands to try, I could
run them and see if I have any comments.

Thanks.





  reply	other threads:[~2020-09-30 18:30 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
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 [this message]
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=837dsbi0bz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34589@debbugs.gnu.org \
    --cc=gustaf.waldemarson@gmail.com \
    --cc=larsi@gnus.org \
    /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).