public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Mark Wielaard <mark@klomp.org>, debugedit@sourceware.org
Subject: Re: [PATCH] scripts/find-debuginfo.in: Add -q|--quiet
Date: Sat, 28 Jan 2023 08:24:06 -0500	[thread overview]
Message-ID: <92604e62-0121-dd93-a7f6-a86bd01dc0dd@redhat.com> (raw)
In-Reply-To: <16f282cf1aef62db202c3cc8902b406dae08e9bc.camel@klomp.org>

On 1/27/23 12:38, Mark Wielaard wrote:
> Hi Prarit,
> 
> On Thu, 2023-01-26 at 16:08 -0500, Prarit Bhargava wrote:
>> Projects with a large number of compiled files end up with a large number
>> of 'extracting debug info from' messages in the build log.  In the case of
>> the Fedora kernel these messages account for 8504 lines in the log, or 61%
>> of the entire log [1].
>>
>> Removing these lines make the log easier to view and comprehend for some
>> projects, however, not all projects will want to silence these messages so
>> suppressing them must be optional.
>>
>> Add a -q|--quiet which allows users to silence the non-error output from
>> the script.
> 
> Looks perfect. Applied as is. Also backported to Fedora rawhide package
> debugedit-5.0-7.fc38 so you can test it out there.
> 

Thanks.  LGTM.  Is there any chance you could also create packages for 
F37 and F36?

https://src.fedoraproject.org/rpms/debugedit

I'd like to add --quiet to the kernel.spec but cannot do so until the 
fix reaches all supported fedora releases.

P.

> Thanks,
> 
> Mark
> 


  reply	other threads:[~2023-01-28 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 21:08 Prarit Bhargava
2023-01-27 17:38 ` Mark Wielaard
2023-01-28 13:24   ` Prarit Bhargava [this message]
2023-01-28 23:07     ` Mark Wielaard

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=92604e62-0121-dd93-a7f6-a86bd01dc0dd@redhat.com \
    --to=prarit@redhat.com \
    --cc=debugedit@sourceware.org \
    --cc=mark@klomp.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).