From: r6144 <r6k@sohu.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH][newbie] Make gdb accept -feliminate-dwarf2-dups stuff
Date: Thu, 15 Jan 2004 03:15:00 -0000 [thread overview]
Message-ID: <16390.1462.203353.461105@localhost.localdomain> (raw)
In-Reply-To: <20040114150704.GA4517@nevyn.them.org>
Daniel Jacobowitz writes:
> Thanks. Unfortunately, we can't fix up and include the patch unless
> you file a copyright assignment with the FSF. You can do that, or wait
> - a whole lot of people have needed this feature lately, and if no one
> with an assignment beats me to it I'll probably do it myself this
> month. I skimmed your patch and it looks like you're doing it rather
> differently than I planned to.
<rant>
Mmm. What a hassle, especially for a young Chinese student who have
hardly seen any international snail mails before. That's partly a
reason when I say I didn't expect the patch to be included. It is so
unlucky that safety and convenience don't go together, and that those
who actually have an assignment are all so busy...
</rant>
Anyway, I have sent a request for the copyright assignment form, but
I'm not really confident that I can complete this formidable (for me)
task. Thank for your kind reply, though.
>
> > +#include <search.h>
>
> Neat, I hadn't seen this before...
It would be great if someday application software such as gcc and gdb
can use Glib... but maybe Glib isn't *that* portable, yet.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-15 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 14:59 r6144
2004-01-14 15:07 ` Daniel Jacobowitz
2004-01-15 3:15 ` r6144 [this message]
2004-01-15 4:39 ` Felix Lee
2004-01-15 4:56 ` Daniel Jacobowitz
2004-01-14 15:23 ` Andrew Cagney
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=16390.1462.203353.461105@localhost.localdomain \
--to=r6k@sohu.com \
--cc=gdb-patches@sources.redhat.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