From: Pedro Alves <palves@redhat.com>
To: Peeter Joot <peeter.joot@gmail.com>, Tom Tromey <tom@tromey.com>
Cc: 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 14:47:00 -0000 [thread overview]
Message-ID: <c218a124-897c-9726-5162-69444cd99a93@redhat.com> (raw)
In-Reply-To: <CAJ4e__j6Yg1_iVeMvPC8oJ_NFvAyPmY_=EWHev4S5vfSw-G3ZA@mail.gmail.com>
On 02/13/2019 02:11 PM, Peeter Joot wrote:
>> Hi! What is the status of this? I'm still interested in getting this
>> patch into gdb.
>>
>
> Hi Tom,
>
> FSF legal is essentially unresponsive about the contribution paperwork that
> we submitted (Oct 2017.)
>
> We last heard from the FSF Licensing & Compliance Manager August 31st last
> year, who stated they were hiring a new administrator, and asked for some
> time to review. Our company legal asked if we could provide any additional
> information to help things along Oct 1st last year, and again Jan 14th this
> year -- I don't believe we received any reply from the FSF.
I'm very sorry to hear that. I'll get in touch with the FSF, see if
we can help unblock this. In my experience copyright assignments are
pretty quick nowadays, except that last year the FSF went through
that administration change, which unfortunately delayed things.
>
> The delays were so extensive that we've opted to use lldb as our backend
> debugger, and have started contributing changes to the lldb/clang/llvm
> stack instead. That said, if the FSF does process our contribution
> paperwork, it is still my intention to rebase my changes against
> binutils/LATEST and submit a patch.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-02-13 14:47 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
2019-02-13 14:11 ` Peeter Joot
2019-02-13 14:47 ` Pedro Alves [this message]
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=c218a124-897c-9726-5162-69444cd99a93@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=peeter.joot@gmail.com \
--cc=peeter.joot@lzlabs.com \
--cc=simark@simark.ca \
--cc=tom@tromey.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.
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).