From: Tom Tromey <tom@tromey.com>
To: Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Aaron Merey <amerey@redhat.com>
Subject: Re: [PATCH v3] gdb: Improve debuginfod progress updates
Date: Thu, 07 Apr 2022 08:54:19 -0600 [thread overview]
Message-ID: <87y20h9c6c.fsf@tromey.com> (raw)
In-Reply-To: <CAJDtP-RVzZfGXtDEyD7RutRVmdWsmiywvRajW_hiy5nuAorC1g@mail.gmail.com> (Aaron Merey via Gdb-patches's message of "Mon, 21 Mar 2022 20:27:22 -0400")
>>>>> "Aaron" == Aaron Merey via Gdb-patches <gdb-patches@sourceware.org> writes:
>> To me it seems like having a "Downloading..." message per .so is no big deal.
>> gdb is often chatty.
Aaron> I'd like to avoid printing a large number of "Downloading..." messages but
Aaron> my solution in this patch comes with the added complexity of message
Aaron> truncation when the terminal isn't wide enough. Unless there is a desire
Aaron> among users to limit these messages this way then maybe it's better to
Aaron> just stick to the cylon-style display you suggested.
Yeah, personally I think having the Downloading message is fine, so
unless there are other contrary views, I'd say go with the simpler code
here.
Tom
prev parent reply other threads:[~2022-04-07 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 0:58 [PATCH v2] gdb/debuginfod: Rework " Aaron Merey
2022-02-09 2:25 ` [PATCH v3] gdb: Improve debuginfod " Aaron Merey
2022-02-14 0:56 ` Patrick Monnerat
2022-02-16 2:09 ` Aaron Merey
2022-02-16 10:38 ` Patrick Monnerat
2022-02-17 16:06 ` Aaron Merey
2022-03-04 18:15 ` Tom Tromey
2022-03-09 1:26 ` Aaron Merey
2022-03-18 19:23 ` Tom Tromey
2022-03-22 0:27 ` Aaron Merey
2022-04-07 14:54 ` Tom Tromey [this message]
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=87y20h9c6c.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amerey@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).