From: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
To: "Guillermo E. Martinez via Libabigail"
<libabigail@sourceware.org>, Dodji Seketeli <dodji@seketeli.org>
Subject: Re: [PATCH] ctf-reader: shows incomplete summary changes
Date: Mon, 02 May 2022 17:50:48 -0500 [thread overview]
Message-ID: <2368997.jE0xQCEvom@sali> (raw)
In-Reply-To: <87fslseygg.fsf@seketeli.org>
On Monday, May 2, 2022 10:38:55 AM CDT Dodji Seketeli wrote:
Hi Dodji,
> Hello Guillermo,
>
>
> "Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org> a
>
> écrit:
>
> > Hello libabigail team,
> >
> > This patch improves the output summary changes using CTF reader,
> >
> > Comments are highly appreciated,
> >
> > Kind Regards,
> > Guillermo
> >
>
> I am sorry, but the patch doesn't apply to the current master branch.Sor
> Also, please add a "Signed-off-by" to the patch.
Sorry, I forget mention that it depends of a couple of patches:
https://sourceware.org/pipermail/libabigail/2022q2/004309.html[1]
https://sourceware.org/pipermail/libabigail/2022q2/004310.html[2]
Sure, in v2 it was added:
https://sourceware.org/pipermail/libabigail/2022q2/004326.html[3]
> Thanks!
>
> [...]
Thanks!!
guillermo
--------
[1] https://sourceware.org/pipermail/libabigail/2022q2/004309.html
[2] https://sourceware.org/pipermail/libabigail/2022q2/004310.html
[3] https://sourceware.org/pipermail/libabigail/2022q2/004326.html
next prev parent reply other threads:[~2022-05-02 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:38 Guillermo E. Martinez
2022-05-02 15:38 ` Dodji Seketeli
2022-05-02 22:50 ` Guillermo E. Martinez [this message]
2022-05-02 22:46 ` [PATCH v2] " Guillermo E. Martinez
2022-05-07 1:43 ` [PATCH v3] " Guillermo E. Martinez
2022-05-13 12:09 ` Dodji Seketeli
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=2368997.jE0xQCEvom@sali \
--to=guillermo.e.martinez@oracle.com \
--cc=dodji@seketeli.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).