From: Joel Brobecker <brobecker@adacore.com>
To: Luca Pizzamiglio <luca.pizzamiglio@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] patches from FreeBSD and FSF copyright papers
Date: Tue, 25 Nov 2014 04:28:00 -0000 [thread overview]
Message-ID: <20141125042806.GL5774@adacore.com> (raw)
In-Reply-To: <CAB88xy_s5Qrz1TXOujE6DLD7bY96HH5gAv-t10T4AkLJCj39gA@mail.gmail.com>
Hi Luca,
> I'm Luca, the current maintainer of the gdb ports in FreeBSD
> (http://www.freshports.org/devel/gdb/)
> To improve the support of FreeBSD in gdb, several patches are applied,
> but I guess it's better to submit these patches to upstream as well.
> AFAIK, this is the right place to submit patches.
>
> At the moment, we have several patches almost ready; I wanna restyle
> them to be conform to GNU-conding-style and submit to upstream.
> The first patch I would like to submit is about 15 lines, but other
> patches will follow.
>
> AFAIK, to submit patches I have to sign the FSF copyright assignment
> from contributors, to avoid GPL violation in gdb.
> I've tried to contact the Patch Champion (reading gdb/MAINTAINERS),
> but I've got a 550 Unrouteable address as answer.
> Who can I contact about FSF papers?
I see that Sergio is already taking excellent care of you,
and we look forward to integrating your patches.
One thing probably worth asking is whether you are the author
of all the patches that you'll be submitting? If not, I am pretty
sure that some form of assignment needs to be done before you can
then assign them to the FSF and contribute them to our tree. We'll
get help from the FSF if needed.
Thank you!
--
Joel
next prev parent reply other threads:[~2014-11-25 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 15:25 Luca Pizzamiglio
2014-11-24 21:03 ` Sergio Durigan Junior
2014-11-25 4:28 ` Joel Brobecker [this message]
2014-11-25 9:14 ` Luca Pizzamiglio
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=20141125042806.GL5774@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luca.pizzamiglio@gmail.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