From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28319] abidw - regression in treatment of anonymous enums in structs
Date: Tue, 11 Jan 2022 18:16:51 +0000 [thread overview]
Message-ID: <bug-28319-9487-pA2ksPFlB6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28319-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28319
--- Comment #7 from gprocida at google dot com ---
If you can achieve a fix for both simultaneously that would be great.
We are approaching an Android release cycle phase transition and would like to
get a new version of the ABI monitoring tools cut very soon. Essentially, we
won't wait for this fix.
If you aren't keen on a flag, then it makes sense for me to take the commit I
posted at https://sourceware.org/pipermail/libabigail/2022q1/004062.html and
invert the default. We can then use this for Android pending a more complete
fix from you, at which point it can be reverted.
This removes any time pressure for a quick fix and ensures we have an easier
time with our next couple of ABI monitoring releases - no need to change glue
scripts, in particular.
I hope that makes sense.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-11 18:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 14:28 [Bug default/28319] New: " gprocida at google dot com
2021-09-08 14:45 ` [Bug default/28319] " gprocida at google dot com
2021-09-08 15:23 ` dodji at redhat dot com
2021-09-08 16:00 ` woodard at redhat dot com
2021-09-21 15:27 ` dodji at redhat dot com
2021-10-08 10:53 ` gprocida at google dot com
2022-01-11 11:30 ` gprocida at google dot com
2022-01-11 12:36 ` gprocida at google dot com
2022-01-11 17:01 ` dodji at redhat dot com
2022-01-11 18:16 ` gprocida at google dot com [this message]
2022-01-12 11:25 ` gprocida at google dot com
2022-01-12 11:59 ` gprocida at google dot com
2022-01-13 11:01 ` gprocida at google dot com
2022-01-13 13:35 ` dodji at redhat dot com
2022-01-13 14:26 ` gprocida at google dot com
2022-01-14 12:38 ` dodji at redhat dot com
2022-01-24 17:06 ` gprocida at google dot com
2022-03-01 11:22 ` Dodji Seketeli
2022-03-01 11:22 ` dodji at seketeli dot org
2022-03-01 14:56 ` gprocida at google dot com
2022-03-01 14:59 ` gprocida at google 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-28319-9487-pA2ksPFlB6@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).