Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: Andrew Cagney <ac131313@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] Added verbosity to dwarf2*
Date: Mon, 03 Feb 2003 15:49:00 -0000	[thread overview]
Message-ID: <3E3E8F80.8000702@suse.cz> (raw)
In-Reply-To: <3E3E8A13.1060902@redhat.com>

Andrew Cagney wrote:
>> Michal Ludvig wrote:
>> this patch adds some more verbosity to GDB's error messages. I've 
>> found it very useful for bugreports, because you can locate the 
>> failing testcase much faster when knowing in what objfile it fails.
>> It also helps GCC developers hunting their bugs in DWARF2 generator.
>>
>> OK to commit to mainline? And to 5.3 branch?
>>
>> Because noone complained for a long time and it's only about changing 
>> some strings, not changing a functionality, I've committed the patch 
>> to both mainline and branch.
> 
> 
> Michael, just FYI, if a patch goes into limbo (as in has an unclear 
> approval status) then the best thing to do is `ping'.

If it was something more than changing some strings I'd 'ping' it, for 
sure. But with this simple patch I decided for commit.
I'm sorry if I should ping it. Should I revert the changes?

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz


  reply	other threads:[~2003-02-03 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 10:34 Michal Ludvig
2002-12-14 13:50 ` [RFA] " Michal Ludvig
2002-12-14 22:18   ` Eli Zaretskii
2002-12-16  5:58     ` Michal Ludvig
2002-12-16 10:43       ` Eli Zaretskii
2003-02-03 14:43 ` [PATCH] " Michal Ludvig
2003-02-03 15:26   ` Andrew Cagney
2003-02-03 15:49     ` Michal Ludvig [this message]
2003-02-03 15:59       ` 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=3E3E8F80.8000702@suse.cz \
    --to=mludvig@suse.cz \
    --cc=ac131313@redhat.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