From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Luca Pizzamiglio <luca.pizzamiglio@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] patches from FreeBSD and FSF copyright papers
Date: Mon, 24 Nov 2014 21:03:00 -0000 [thread overview]
Message-ID: <87h9xoia4r.fsf@redhat.com> (raw)
In-Reply-To: <CAB88xy_s5Qrz1TXOujE6DLD7bY96HH5gAv-t10T4AkLJCj39gA@mail.gmail.com> (Luca Pizzamiglio's message of "Mon, 24 Nov 2014 16:25:24 +0100")
On Monday, November 24 2014, Luca Pizzamiglio wrote:
> Hi people,
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.
Yeah, this is the right place. And thank you very much for deciding to
submit them, much appreciated!
> 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 will send you the form offlist :-).
Cheers,
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2014-11-24 21:03 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 [this message]
2014-11-25 4:28 ` Joel Brobecker
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=87h9xoia4r.fsf@redhat.com \
--to=sergiodj@redhat.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