From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29360] Ada ranges emitting/reading/diffing are not supported in libabigail
Date: Fri, 07 Apr 2023 18:16:26 +0000 [thread overview]
Message-ID: <bug-29360-9487-1srrtH3eBQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29360-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29360
Bug 29360 depends on bug 29333, which changed state.
Bug 29333 Summary: fedabipkgdiff --self-compare asserts on Gtk3Ada and Gtk3Ada
https://sourceware.org/bugzilla/show_bug.cgi?id=29333
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-07 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 15:50 [Bug default/29360] New: " dodji at redhat dot com
2022-07-12 15:55 ` [Bug default/29360] " dodji at redhat dot com
2023-04-06 11:20 ` dodji at redhat dot com
2023-04-06 11:21 ` dodji at redhat dot com
2023-04-07 18:16 ` dodji at redhat dot com [this message]
2023-04-07 18:17 ` dodji at redhat 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-29360-9487-1srrtH3eBQ@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).