Leandro Lucarella wrote:
GDB people have spoken (I don't see you subscribed to the bug report so
I transcribe the comment from GDB):
--------------------------------------------------------------------------
For a patch this size we would need copyright assignments from all
the authors of the patch. I would suggest emailing the gdb list
and asking for the paperwork; one of the maintainers will get you started.
Also, send the patch to the gdb-patches list, as described here:
http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/gdb/CONTRIBUTE?content-type=text/x-cvsweb-markup&cvsroot=src
gdb doesn't really use bugzilla for patch tracking, much.
I glanced quickly at the patch; it will need some reformatting and it will
need to be rebased to the current cvs. It may require other changes, too,
but I didn't read that closely.
--------------------------------------------------------------------------
When all licensing issues are resolved I can do any adjustments to the
patch to comply with GDB coding style and rebase it to current CVS if the
original author is missing.
If the original author is missing, you have a bigger problem. He presumably
needs to sign the paperwork they mentioned...
