Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [RFA 2/2] PR cli/19551 - change formatting of "Reading symbols"  messages
Date: Thu, 27 Apr 2017 23:16:00 -0000	[thread overview]
Message-ID: <87zif130hp.fsf@tromey.com> (raw)
In-Reply-To: <c5751eb6ffcf4efbe1a5cf38d7127657@polymtl.ca> (Simon Marchi's	message of "Thu, 27 Apr 2017 17:40:17 -0400")

>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:

Simon> However, I think that feature would deserve a patch of its own
Simon> with a more expressive title.  I am sure many people will be
Simon> interested, but like this it's hidden under some obscure bug fix.

I imagine most users don't read the history but rather would notice when
gdb's behavior changes.

Simon> Would it be possible to make this patch a simple bug fix and put the
Simon> progress bar in a patch of its own?

I guess it would require some delayed output machinery, like what is in
this patch.  I don't really see the benefit of doing this transform --
it seems like a good amount of work for the same result in the end.
However, I don't mind if you, or someone else, wants to take this over.

thanks,
Tom


  reply	other threads:[~2017-04-27 23:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  4:17 [RFA 0/2] Fix PR cli/19551 Tom Tromey
2017-04-13  4:17 ` [RFA 2/2] PR cli/19551 - change formatting of "Reading symbols" messages Tom Tromey
2017-04-18 17:43   ` Pedro Alves
2017-04-18 17:44     ` Pedro Alves
2017-04-20  0:11     ` Tom Tromey
2017-04-27 21:40   ` Simon Marchi
2017-04-27 23:16     ` Tom Tromey [this message]
2017-04-27 23:53       ` Simon Marchi
2017-05-29 17:24     ` Tom Tromey
2017-04-13  4:44 ` [RFA 1/2] Use a distinguishing name for minidebug objfile Tom Tromey
2017-04-18 17:42   ` Pedro Alves
2017-04-19  3:11     ` Tom Tromey

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=87zif130hp.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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