public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Ben Woodard <woodard@redhat.com>
To: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
Cc: Ben Woodard via Libabigail <libabigail@sourceware.org>
Subject: Re: [PATCH v2] ctf-reader: Add support to undefined forward declaration types
Date: Mon, 25 Apr 2022 12:45:45 -0700	[thread overview]
Message-ID: <DA2557CC-F9A1-4530-93DE-84474AA0FDB1@redhat.com> (raw)
In-Reply-To: <2824988.e9J7NaK4W3@sali>

I’ve seen several internal emails from Dodji suggesting that he’s aware of the growing patch queue. I have a couple of patches pending myself. I believe right now he’s really trying to land the fixes branch but before he does that, he needs to fix the 37 or so regressions that I reported to him with that branch. I think that kind of derailed his plans to merge the fixes branch, run through the patch queue, and then release 2.1. I don’t think he’s ignoring you, it is just I through a spanner in the works.

-ben

> On Apr 25, 2022, at 11:37 AM, Guillermo E. Martinez via Libabigail <libabigail@sourceware.org> wrote:
> 
> On Thursday, March 17, 2022 7:30:36 PM CDT Guillermo E. Martinez wrote:
> Hello libabigail team,
> 
> Any comment about this patch?
> 
> Thanks,
> Guillermo
> 
>> Undefined struct/union forward declaration types are not serialized in
>> abixml representation using `class-decl' node.
>> 
>> For instance, consider:
>> 
>>    struct key_type;
>>    typedef void (*key_restrict_link_func_t)(struct key_type *type);
>> 
>> Expected node:
>> 
>> [..]
> 
> 


  reply	other threads:[~2022-04-25 19:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12  4:14 [PATCH] " Guillermo E. Martinez
2022-03-17  4:49 ` Guillermo Martinez
2022-03-18  1:30 ` [PATCH v2] " Guillermo E. Martinez
2022-03-31 21:12   ` Guillermo Martinez
2022-04-04 22:51     ` Guillermo Martinez
2022-04-25 18:37   ` Guillermo E. Martinez
2022-04-25 19:45     ` Ben Woodard [this message]
2022-04-25 20:24       ` Guillermo E. Martinez
2022-04-29 10:57   ` Dodji Seketeli
2022-04-29 13:50     ` Guillermo E. Martinez

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=DA2557CC-F9A1-4530-93DE-84474AA0FDB1@redhat.com \
    --to=woodard@redhat.com \
    --cc=guillermo.e.martinez@oracle.com \
    --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).