From: Mark Wielaard <mark@klomp.org>
To: Robert Dubner <rdubner@symas.com>
Cc: gdb@sourceware.org
Subject: Re: Legal assigment forms for GDB
Date: Thu, 22 Feb 2024 22:38:09 +0100 [thread overview]
Message-ID: <20240222213809.GE12488@gnu.wildebeest.org> (raw)
In-Reply-To: <015101da65cf$48f6a410$dae3ec30$@symas.com>
Hi Bob,
On Thu, Feb 22, 2024 at 02:39:51PM -0600, Robert Dubner wrote:
> I anticipate making contributions to GDB on an ongoing basis. Apparently
> there are forms the FSF wants filled out, and according to
> https://sourceware.org/gdb/wiki/ContributionChecklist, I am supposed to
> ask for them here.
>
> I hereby request any forms I need.
I saw you made the same request for GCC. You can use the same
request-assign.future for both GCC and GDB:
https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future
Just say GCC and GDB under
[What is the name of the program or package you're contributing to?]
Then just sent a copy to assign@gnu.org
Cheers,
Mark
next prev parent reply other threads:[~2024-02-22 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 20:39 Robert Dubner
2024-02-22 21:38 ` Mark Wielaard [this message]
2024-02-22 23:26 ` Robert Dubner
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=20240222213809.GE12488@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=gdb@sourceware.org \
--cc=rdubner@symas.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).