public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrei Pikas <gdb@mail.api.win>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v6] Add an option with a color type.
Date: Sat, 11 May 2024 18:17:02 +0300	[thread overview]
Message-ID: <cf42c444-a70c-4396-904f-e4a35d6139cb@mail.api.win> (raw)
In-Reply-To: <87le57gadm.fsf@tromey.com>

Hi. I have signed copyright assignment on April 30th and sent it to 
assign@gnu.org. They wrote: "Once the FSF has signed it, we will send 
you a digital copy in PDF format for your records". But I haven't 
received a response yet. I don't know whether I should wait for a copy 
signed by the FSF or not.


On 20/04/2024 21:24, Tom Tromey wrote:
>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
> Tom> We have to have some paperwork before we can accept large patches.
> Tom> Email 'assign@gnu.org' and say that you have a patch submission to gdb.
> Tom> They will get you started on the process.
>
> I forgot to mention -- please keep us informed.  We may not get any
> notice if/when your assignment is complete.
>
> Tom

  parent reply	other threads:[~2024-05-11 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 11:40 [PATCH v4] " Andrei Pikas
2022-10-16 13:45 ` Eli Zaretskii
2022-10-16 16:03   ` [PATCH v5] " Andrei Pikas
2022-10-16 16:22     ` Eli Zaretskii
2022-10-16 16:28       ` [PATCH v6] " Andrei Pikas
2022-10-16 16:45         ` Eli Zaretskii
2024-04-19 19:33         ` Tom Tromey
2024-04-19 19:52           ` Andrei Pikas
2024-04-19 20:19             ` Tom Tromey
2024-04-20 18:24               ` Tom Tromey
2024-04-20 18:32                 ` Andrei Pikas
2024-05-11 15:17                 ` Andrei Pikas [this message]
2024-05-13 19:02                   ` Tom Tromey
2024-05-21  9:00                     ` Andrei Pikas

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=cf42c444-a70c-4396-904f-e4a35d6139cb@mail.api.win \
    --to=gdb@mail.api.win \
    --cc=gdb-patches@sourceware.org \
    --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).