From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Tristan Gingold <gingold@adacore.com>,
Fawzi Mohamed <fawzi.mohamed@nokia.com>
Subject: Re: patches for mac support
Date: Fri, 24 Jun 2011 11:09:00 -0000 [thread overview]
Message-ID: <201106241208.46760.pedro@codesourcery.com> (raw)
In-Reply-To: <3634A65E-25ED-4F1F-8D22-AD3FCEAF2C9B@adacore.com>
On Friday 24 June 2011 10:38:08, Tristan Gingold wrote:
> Note that you need to properly submit your patches: one patch by mail is better (IMHO), patch should be inlined if not large, and
> you need ChangeLog entries. I suppose the instructions are on the web, also I don't know where.
<http://www.gnu.org/software/gdb/>, follow [contributing] at the top.
--
Pedro Alves
next prev parent reply other threads:[~2011-06-24 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 20:07 Fawzi Mohamed
2011-06-24 9:38 ` Tristan Gingold
2011-06-24 11:09 ` Pedro Alves [this message]
2011-06-26 0:23 ` fawzi.mohamed
2011-06-27 8:59 ` Tristan Gingold
2011-06-27 9:18 ` Fawzi Mohamed
2011-06-27 9:46 ` André Pönitz
2011-06-27 15:59 ` Fawzi Mohamed
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=201106241208.46760.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=fawzi.mohamed@nokia.com \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.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