From: Eli Zaretskii <eliz@gnu.org>
To: Matheus Branco Borella <dark.ryu.550@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add name_of_main and language_of_main to the DWARF index
Date: Fri, 07 Jul 2023 21:00:25 +0300 [thread overview]
Message-ID: <835y6vfvpi.fsf@gnu.org> (raw)
In-Reply-To: <20230707150021.618-1-dark.ryu.550@gmail.com> (message from Matheus Branco Borella on Fri, 7 Jul 2023 12:00:22 -0300)
> From: Matheus Branco Borella <dark.ryu.550@gmail.com>
> Cc: gdb-patches@sourceware.org,
> Matheus Branco Borella <dark.ryu.550@gmail.com>
> Date: Fri, 7 Jul 2023 12:00:22 -0300
>
> Eli Zaretskii <eliz@gnu.org> wrote:
> > Your assignment is not on file yet, AFAICT. Was the paperwork
> > completed, i.e. did you get a copy of the assignment signed by you and
> > by the FSF? If not, you need to wait some more.
>
> Huh, that's weird. I do have the copy, signed by both parties. Maybe it just
> hasn't been filed yet? If you want, I could forward it to you.
I see now that your assignment was added, but it's only for Emacs, not
for GDB.
> > Thanks. The documentation parts are OK, but please fix the text to
> > leave two spaces between sentences, not one.
>
> Alright, I've fixed that.
>
> Is there anything else I'm missing?
There's still the issue of copyright assignment for GDB contributions,
AFAICT.
next prev parent reply other threads:[~2023-07-07 18:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 21:40 Matheus Branco Borella
2023-06-09 16:56 ` Tom Tromey
2023-06-30 20:36 ` Matheus Branco Borella
2023-07-01 5:47 ` Eli Zaretskii
2023-07-07 15:00 ` Matheus Branco Borella
2023-07-07 18:00 ` Eli Zaretskii [this message]
2023-08-04 20:55 ` Tom de Vries
2023-08-05 5:36 ` Eli Zaretskii
2023-08-03 7:12 ` Tom de Vries
2023-08-03 7:29 ` Tom de Vries
2023-08-04 18:09 ` [PATCH v2] " Matheus Branco Borella
2023-08-11 18:21 ` [PATCH v3] " Matheus Branco Borella
2023-08-14 7:31 ` Tom de Vries
2023-08-14 7:36 ` Tom de Vries
2023-09-13 7:09 ` Tom de Vries
2023-09-25 18:47 ` Matheus Branco Borella (DarkRyu550)
2023-09-26 14:07 ` Tom de Vries
2023-10-04 22:30 ` Tom de Vries
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=835y6vfvpi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dark.ryu.550@gmail.com \
--cc=gdb-patches@sourceware.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.
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).