From: Tom Tromey <tom@tromey.com>
To: Peeter Joot <peeter.joot@gmail.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org,
Peeter Joot <peeter.joot@lzlabs.com>,
Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH] review request: implementing DW_AT_endianity
Date: Wed, 13 Feb 2019 13:12:00 -0000 [thread overview]
Message-ID: <87sgwr6de7.fsf@tromey.com> (raw)
In-Reply-To: <CAJ4e__gakTnAPc9dN01EXF+pT43DMdZBJQKYNPYGra7RW5sAtQ@mail.gmail.com> (Peeter Joot's message of "Thu, 22 Feb 2018 12:39:03 -0500")
>>>>> "Peeter" == Peeter Joot <peeter.joot@gmail.com> writes:
Peeter> I'm still holding the patch for submission. I'd handled all the reviewer
Peeter> comments I received, implemented the tests suggestion by the reviewers, and
Peeter> verified that I introduced no test regressions. Also, the gcc side issues
Peeter> I noticed testing this are already fixed in the latest version (trunk, but
Peeter> perhaps one of the releases now too).
Peeter> Unfortunately, the FSF attribution required for me to submit this formally
Peeter> on behalf of the company I work for has been delayed repeatedly. The last
Peeter> I heard from the company lawyer who was arranging the attribution is that
Peeter> there's just a few more i's and t's to dot and cross, but it should be done
Peeter> soon.
Hi! What is the status of this? I'm still interested in getting this
patch into gdb.
thanks,
Tom
next prev parent reply other threads:[~2019-02-13 13:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 15:06 Peeter Joot
2017-10-06 21:18 ` Peeter Joot
2017-10-08 18:41 ` Simon Marchi
2017-10-09 9:11 ` Peeter Joot
2017-10-09 12:12 ` Simon Marchi
2017-10-10 18:16 ` Peeter Joot
2017-10-10 18:33 ` Simon Marchi
2017-10-10 18:38 ` Peeter Joot
2017-10-10 18:48 ` Simon Marchi
2017-10-10 19:38 ` Peeter Joot
2017-10-10 23:30 ` [PATCH] " Peeter Joot
2017-10-11 2:29 ` Peeter Joot
2017-10-12 20:23 ` Simon Marchi
2018-02-22 17:20 ` Tom Tromey
2018-02-22 17:39 ` Peeter Joot
2019-02-13 13:12 ` Tom Tromey [this message]
2019-02-13 14:11 ` Peeter Joot
2019-02-13 14:47 ` Pedro Alves
2019-02-13 16:19 ` Pedro Alves
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=87sgwr6de7.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=peeter.joot@gmail.com \
--cc=peeter.joot@lzlabs.com \
--cc=simark@simark.ca \
/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