public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19103] New: make abidw --abidiff output on stdout rather than stderr
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <bug-19103-9487@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=19103

            Bug ID: 19103
           Summary: make abidw --abidiff output on stdout rather than
                    stderr
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: woodard at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

in the case where abidw is run with the --abidiff it would be helpful if it
emitted its output on stdout rather than stderr. It makes scripting harder, it
splitting off the aborts vs. the abixml correctness issues more difficult and
it forces me to use a command like:

~/bin/abidw --abidiff
/collab/usr/global/tools/order/spack/opt/chaos_5_x86_64_ib/gcc@4.4.7/dyninst@8.2.1-a77e6bbb/lib/libpcontrol.so.8.2.1
2>&1 | less

rather than the normal piping. Since nothing is being printed when you are
doing an abidw --abidiff unless it is a change that must be what you are
looking for when you use the --abidiff option.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2015-10-09  0:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 woodard at redhat dot com [this message]
2016-01-01  0:00 ` [Bug default/19103] " woodard at redhat dot com
2020-11-11 15:50 ` maennich at android dot com

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-19103-9487@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).