From: Joel Brobecker <brobecker@adacore.com>
To: Noam Yorav-Raphael <noamraph@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Sent a patch to the bug database - Retrieve long long from Python
Date: Tue, 01 Sep 2009 16:23:00 -0000 [thread overview]
Message-ID: <20090901162245.GB4365@adacore.com> (raw)
In-Reply-To: <b348a0850909010055n19c8f9e5o174061c8c2d0d471@mail.gmail.com>
> Is this ok? Do you prefer that I send patches like this directly to
> this mailing list?
It certainly makes it easier for us to review your patches if you
send them to this list. Can you also write a testcase for your patch,
so that we don't accidently regress?
Thanks,
--
Joel
next prev parent reply other threads:[~2009-09-01 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 7:56 Noam Yorav-Raphael
2009-09-01 16:23 ` Joel Brobecker [this message]
2009-09-01 17:35 ` Tom Tromey
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=20090901162245.GB4365@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=noamraph@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