Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: -file-list-exec-source-files
Date: Wed, 21 Apr 2004 04:58:00 -0000	[thread overview]
Message-ID: <20040420143031.GA4605@white> (raw)

Hi,

Will someone please review this patch?
Why is no one looking at it?
I have not received one reply to my pings in 2 months.  Why?
What else should I do?

Does everyone realize the potential GDB throws away every day by not
reviewing patches in a reasonable time. When I wrote that patch, I was
interested in making the stack,breakpoint,... output show the fullname.
As of right now, I am no longer interested in doing that, or anything else
that isn't necessary for me to write CGDB.

I had many other ideas that I wanted to implement in GDB. As of know, I
am no longer interested. Maybe my mind will change in the future, but I
can't stand the thought of this long patch review time.

Every time I ping for this patch I laugh. I can't even imagine what is
wrong with the GDB team to think that my trivial 500 line patch takes 2
months to begin reviewing. I wrote that patch in about 1 week, with out
ever doing a major patch to GDB before. What's going on?

Anyways, if this Email feels a little negative, it's coming from the
frustration of waiting and waiting to get a patch into GDB. To me, it
won't be worth it to go through this process again if I don't need to.

Finally, the GDB team actually was very helpful to me when I was coming
up with the -file-list-exec-source-files patch. I received answers very
quickly, and with more information than I could have hoped for. Everyone
seems to want to help out during the development and research phase. It
just seems that when it comes to patch time, all bets are off

Bob Rossi


                 reply	other threads:[~2004-04-21  1:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040420143031.GA4605@white \
    --to=bob@brasko.net \
    --cc=gdb@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