From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING*3][PATCH v4] gdb: Improve debuginfod progress updates
Date: Thu, 13 Oct 2022 00:02:27 +0200 [thread overview]
Message-ID: <CAJVr-EN=KE9MoC6_B=Z4LcDVTTMkhq4J5T3ea3bpc2en-ndUtA@mail.gmail.com> (raw)
In-Reply-To: <20221012185327.370210-1-amerey@redhat.com>
On Wed, Oct 12, 2022 at 8:54 PM Aaron Merey via Gdb-patches <
gdb-patches@sourceware.org> wrote:
> Hi,
>
> I made a couple small adjustments to this patch to ensure it builds
> on the main branch. Otherwise the original v4 patch follow:
>
> v3 can be found here:
> https://sourceware.org/pipermail/gdb-patches/2022-February/185798.html
>
> Changes from v3 include a simplified progress update API and display.
> Truncation of the progress update message has been removed as well.
>
> If the download size is known, a progress bar is displayed along with
> the percentage of completion and the total download size.
>
> Downloading separate debug info for /lib/libxyz.so
> [############ ] 25% (10.01 MB)
>
> If the download size is not known, a progress indicator is displayed
> with a ticker ("###") that moves across the screen at a rate of 1 tick
> every 0.5 seconds.
>
> Downloading separate debug info for /lib/libxyz.so
> [ ### ]
>
> I think this version addresses all the concernes from the previous
> iterations and I
>
confirm it applies on top of the current master cleanly, it should be good
to go.
WARNING: multiple messages have this Message-ID
From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING*3][PATCH v4] gdb: Improve debuginfod progress updates
Date: Thu, 13 Oct 2022 00:02:27 +0200 [thread overview]
Message-ID: <CAJVr-EN=KE9MoC6_B=Z4LcDVTTMkhq4J5T3ea3bpc2en-ndUtA@mail.gmail.com> (raw)
Message-ID: <20221012220227.iuKw9U5fFf-2j6To9JV0obgkDFGpfOzWvB9If-bKAro@z> (raw)
In-Reply-To: <20221012185327.370210-1-amerey@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Wed, Oct 12, 2022 at 8:54 PM Aaron Merey via Gdb-patches <
gdb-patches@sourceware.org> wrote:
> Hi,
>
> I made a couple small adjustments to this patch to ensure it builds
> on the main branch. Otherwise the original v4 patch follow:
>
> v3 can be found here:
> https://sourceware.org/pipermail/gdb-patches/2022-February/185798.html
>
> Changes from v3 include a simplified progress update API and display.
> Truncation of the progress update message has been removed as well.
>
> If the download size is known, a progress bar is displayed along with
> the percentage of completion and the total download size.
>
> Downloading separate debug info for /lib/libxyz.so
> [############ ] 25% (10.01 MB)
>
> If the download size is not known, a progress indicator is displayed
> with a ticker ("###") that moves across the screen at a rate of 1 tick
> every 0.5 seconds.
>
> Downloading separate debug info for /lib/libxyz.so
> [ ### ]
>
> I think this version addresses all the concernes from the previous
> iterations and I
>
confirm it applies on top of the current master cleanly, it should be good
to go.
next prev parent reply other threads:[~2022-10-12 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 23:46 Aaron Merey
2022-10-12 18:53 ` Aaron Merey
2022-10-12 22:02 ` Alexandra Petlanova Hajkova [this message]
2022-10-12 22:02 ` Alexandra Petlanova Hajkova
2022-10-21 16:42 ` [PING*4][PATCH " Aaron Merey
2022-10-21 20:01 ` Tom Tromey
2022-10-26 3:17 ` [PATCH v4] gdb/debuginfod: Improve " Aaron Merey
2022-11-09 20:02 ` Tom Tromey
2022-11-10 17:20 ` Aaron Merey
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='CAJVr-EN=KE9MoC6_B=Z4LcDVTTMkhq4J5T3ea3bpc2en-ndUtA@mail.gmail.com' \
--to=ahajkova@redhat.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).