From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27278] Stray non-diff
Date: Mon, 26 Jul 2021 15:57:51 +0000 [thread overview]
Message-ID: <bug-27278-9487-YSrtl8v5dC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27278-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27278
gprocida at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gprocida at google dot com
--- Comment #4 from gprocida at google dot com ---
I've rechecked the a.xml b.xml case with latest upstream master
(cfd81dec10b26759b08c60c59b0d32f905d9913f).
I get similarly bad output with plain abidiff and similarly good output with
abidiff --leaf-changes-only.
Note
We are now post-processing all abidw-generated XML for more recent Android
kernels with a utility that tidies the XML in various ways, mostly so that XML
diffs are more predictable.
The tidied XML has no harmful diffs with or without --leaf-changes-only. I'm
not sure which of the various passes contributed to this, but I can dig further
if that's of interest.
We will likely no longer spot or report issues that go away after XML tidying.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-07-26 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 16:45 [Bug default/27278] New: " gprocida+abigail at google dot com
2021-02-01 14:22 ` [Bug default/27278] " gprocida+abigail at google dot com
2021-04-13 9:52 ` gprocida+abigail at google dot com
2021-05-11 10:13 ` gprocida+abigail at google dot com
2021-07-26 15:57 ` gprocida at google 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-27278-9487-YSrtl8v5dC@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).