From: Kevin Buettner <kevinb@redhat.com>
To: "Levchenko, Vasily V" <vasily.v.levchenko@intel.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Relative and absolute paths in link_map
Date: Thu, 17 Feb 2005 17:13:00 -0000 [thread overview]
Message-ID: <20050217091415.1f48a6c1@ironwood.lan> (raw)
In-Reply-To: <9F0F5F4271FA9140BE3E05452E3BDAFE7F3070@mssmsx403.ccr.corp.intel.com>
On Thu, 17 Feb 2005 18:20:43 +0300
"Levchenko, Vasily V" <vasily.v.levchenko@intel.com> wrote:
> This is a patch corrects comparing of the shared object names which
> could be relative and absolute.
> Situation:
> To get tls-variable from shared library.
Hi Vasily,
Thanks for your patch!
In the future, please send some sort of context diff, that is, patches
generated either with "diff -u" or "diff -C". (I also like it when the
"-p" switch is used.)
I have read your patch and understand what it is doing, but before
putting your change in, I'd first like to understand why it's necessary.
Could you offer a bit more explanation about why it is needed? Do you
happen to have a small test case?
Your patch is small enough that it can likely go in without an FSF
copyright assignment. You should know, however, that most patches
require some sort of copyright assignment. If you think you might
make further contributions to GDB in the future, you should make the
proper legal arrangements. If this is something that you're
interested in, let me know, and I will ask to have the necessary
documents sent to you.
Again, I thank you for your patch, and hope that you can provide me
with the some sort of test case or at least a description of the
scenario in which your patch is needed.
Kevin
next prev parent reply other threads:[~2005-02-17 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 16:59 Levchenko, Vasily V
2005-02-17 17:13 ` Kevin Buettner [this message]
2005-02-17 23:48 ` Daniel Jacobowitz
2005-02-18 2:32 ` Kevin Buettner
2005-02-18 16:51 Levchenko, Vasily V
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=20050217091415.1f48a6c1@ironwood.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vasily.v.levchenko@intel.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