From: sahilcdq via Gdb <gdb@sourceware.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Request for copyright assignment form
Date: Sat, 06 Jul 2024 10:09:46 +0000 [thread overview]
Message-ID: <_aRydrVEEklSex1y7pb3C8PQHxi-C1hmDVvYXLHML_zBnFw1A-3KV-H23cGiZZWQMRH14E2bgCeXzptwFxv5tH4E_E6bt0QZoN_dTRNLrnE=@proton.me> (raw)
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,
Sahil
[1] https://sourceware.org/pipermail/gdb-patches/2024-July/210374.html
[2] http://web.cvs.savannah.gnu.org/viewvc/gnulib/gnulib/Copyright/request-assign.future?view=markup
next reply other threads:[~2024-07-06 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 10:09 sahilcdq via Gdb [this message]
2024-07-06 11:08 ` Mark Wielaard
2024-07-06 11:15 ` Eli Zaretskii via Gdb
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='_aRydrVEEklSex1y7pb3C8PQHxi-C1hmDVvYXLHML_zBnFw1A-3KV-H23cGiZZWQMRH14E2bgCeXzptwFxv5tH4E_E6bt0QZoN_dTRNLrnE=@proton.me' \
--to=gdb@sourceware.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