Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dave Murphy <wintermute2k4@ntlworld.com>
To: gdb@sourceware.org
Subject: GDB patches for mingw host
Date: Sun, 01 Jul 2007 15:43:00 -0000	[thread overview]
Message-ID: <4687CB97.8010304@ntlworld.com> (raw)

Hi,

I have a set of patches which allow GBB 6.6 to be built using MinGW/MSys 
for a mingw host which I would like to contribute for consideration.

 From reading through the contribution requirements it seems that I need 
an FSF assignment on file before submitting patches. It's not clear to 
me how to request the necessary paperwork, perhaps I'm just looking in 
the wrong place.

Is it sufficient to request paperwork via the list and do I need to do 
this for each project I wish to submit patches for? I have some minor 
patches for Insight, gcc and some more extensive work I'd like the 
newlib maintainers to consider.

Would it be preferable to create the gdb patches against CVS before 
submission?

Dave Murphy


             reply	other threads:[~2007-07-01 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 15:43 Dave Murphy [this message]
2007-07-01 19:50 ` Eli Zaretskii
2007-07-01 20:50   ` Daniel Jacobowitz

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=4687CB97.8010304@ntlworld.com \
    --to=wintermute2k4@ntlworld.com \
    --cc=gdb@sourceware.org \
    /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