From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [patch]: User choice for multiply-defined symbols
Date: Mon, 05 May 2008 12:58:00 -0000 [thread overview]
Message-ID: <20080505114545.GA22274@caradoc.them.org> (raw)
In-Reply-To: <481EBD33.6090704@de.ibm.com>
On Mon, May 05, 2008 at 09:54:27AM +0200, Markus Deuling wrote:
> Hello,
>
> the following patch makes use of the new "multiple-symbols" command introduced by Joel.
Hi Markus,
I'm totally confused by this explanation. What case are you handling
and what does it output before and after your patch?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-05 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 8:36 Markus Deuling
2008-05-05 9:06 ` Vladimir Prus
2008-05-05 10:11 ` Markus Deuling
2008-05-05 12:58 ` Daniel Jacobowitz [this message]
2008-05-07 11:36 ` Markus Deuling
2008-05-07 22:00 ` Daniel Jacobowitz
2008-05-08 11:43 ` Markus Deuling
2008-05-08 16:33 ` Eli Zaretskii
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=20080505114545.GA22274@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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