From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Jean-Marc Saffroy <saffroy@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] refreshed patch for PR 11804 and PR 9904
Date: Sat, 28 Jul 2012 07:10:00 -0000 [thread overview]
Message-ID: <20120728071023.GA5790@host2.jankratochvil.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1207180238040.5348@erda.mds>
Hello Jean-Marc,
besides the technical part see the file 'gdb/CONTRIBUTE', GDB patches require
FSF ChangeLog entries:
http://www.gnu.org/prep/standards/standards.html#Change-Logs
And this patch is large enough to require FSF GDB copyright assignment, you
can get the snail-mail form from:
Sergio Durigan Junior <sergiodj@redhat.com>
Still we can work on the patch in the meantime, the copyright assignment is
needed only before the final check-in.
Thanks,
Jan
next prev parent reply other threads:[~2012-07-28 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 0:50 Jean-Marc Saffroy
2012-07-28 7:05 ` Jan Kratochvil
2012-07-29 17:11 ` Jean-Marc Saffroy
2012-07-29 17:35 ` Jean-Marc Saffroy
2012-07-31 13:21 ` Jan Kratochvil
2012-08-07 13:27 ` [commit] " Jan Kratochvil
2012-07-28 7:10 ` Jan Kratochvil [this message]
2012-07-31 13:23 ` Jan Kratochvil
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=20120728071023.GA5790@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=saffroy@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