From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30274] RFE have fedabipkgdiff prefer debuginfod when available
Date: Sun, 26 Mar 2023 14:24:23 +0000 [thread overview]
Message-ID: <bug-30274-9487-oAaC03Sxxf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30274-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30274
--- Comment #2 from Ben Woodard <woodard at redhat dot com> ---
One thing that I can say from experience is when there are a lot of
differences, the size of output files is a few hundred thousand lines and
probably amounts to a couple of megabytes of text. This is tiny in relation to
the size of memory used by abipkgdiff itself when building the corpus. (I've
seen up to 25G just casually watching top.) So to me it sounds like the concern
that led to that design decision is unwarranted.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-03-26 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 1:40 [Bug default/30274] New: " woodard at redhat dot com
2023-03-26 3:18 ` [Bug default/30274] " fche at redhat dot com
2023-03-26 14:24 ` woodard at redhat dot com [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=bug-30274-9487-oAaC03Sxxf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).