From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: sahilcdq <sahilcdq@proton.me>
Cc: gdb@sourceware.org
Subject: Re: Request for copyright assignment form
Date: Sat, 06 Jul 2024 14:15:46 +0300 [thread overview]
Message-ID: <86frsm4vq5.fsf@gnu.org> (raw)
In-Reply-To: <_aRydrVEEklSex1y7pb3C8PQHxi-C1hmDVvYXLHML_zBnFw1A-3KV-H23cGiZZWQMRH14E2bgCeXzptwFxv5tH4E_E6bt0QZoN_dTRNLrnE=@proton.me> (message from sahilcdq via Gdb on Sat, 06 Jul 2024 10:09:46 +0000)
> Date: Sat, 06 Jul 2024 10:09:46 +0000
> From: sahilcdq via Gdb <gdb@sourceware.org>
>
> Hi,
>
> I have never contributed to gdb but am interested in
> contributing to it in the long run.
>
> I have one patch ready [1] and have been informed that
> I'll need to complete a "copyright assignment" process
> before the changes can be merged. I found this request
> form [2] for past and future changes in gnulib's repo.
> I am not sure if this is just a sample form or if it's
> appropriate for gdb-related changes.
>
> Where might I find the relevant FSF copyright assignment
> request form?
Thanks, form sent off-list.
prev parent reply other threads:[~2024-07-06 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 10:09 sahilcdq via Gdb
2024-07-06 11:08 ` Mark Wielaard
2024-07-06 11:15 ` Eli Zaretskii via Gdb [this message]
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=86frsm4vq5.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=eliz@gnu.org \
--cc=sahilcdq@proton.me \
/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