From: Joel Brobecker <brobecker@adacore.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Remove exec_set_section_offsets
Date: Sat, 19 Apr 2008 05:57:00 -0000 [thread overview]
Message-ID: <20080419021241.GO12735@adacore.com> (raw)
In-Reply-To: <1208570812.5808.113.camel@localhost.localdomain>
> Nice to know, thanks for the tip. So if I observe that, this kind of
> patch fits the obvious rule?
Yes :).
--
Joel
prev parent reply other threads:[~2008-04-19 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 0:34 Thiago Jung Bauermann
2008-04-19 4:28 ` Joel Brobecker
2008-04-19 4:28 ` Thiago Jung Bauermann
2008-04-19 5:57 ` Joel Brobecker [this message]
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=20080419021241.GO12735@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@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