From: Dodji Seketeli <dodji@seketeli.org>
To: Matthias Maennich <maennich@google.com>
Cc: libabigail@sourceware.org, gprocida@google.com,
kernel-team@android.com
Subject: Re: [PATCH] abidiff: improve whitespace generation in symbol diff report
Date: Wed, 19 Jan 2022 15:04:33 +0100 [thread overview]
Message-ID: <87fspjbz4e.fsf@seketeli.org> (raw)
In-Reply-To: <20211126110642.4164044-1-maennich@google.com> (Matthias Maennich's message of "Fri, 26 Nov 2021 11:06:42 +0000")
Matthias Maennich <maennich@google.com> a écrit:
> maybe_report_diff_for_symbol() has a few issues:
>
> 1. The responsibility for newline emission is somewhat unclear and
> indeed it would emit spurious blank lines before most of the
> sub-diffs it reports.
>
> 2. Different sub-diff text and terminal commas are emitted according to
> whether or not there had been a previous sub-diff - making the output
> harder to grep and post-process.
>
> 3. The function also returns a bool but that return value is never used.
>
> Hence, change the function to return void, the function stanzas to
> always emit newline-terminated lines and ensure the wording and
> punctuation of each sub-diff do not vary. This also tweaks (shortens)
> the wording used for CRC diffs.
>
> * src/abg-reporter-priv.cc (maybe_report_diff_for_symbol):
> Make return void. Simplify and fix new-line emission. Remove
> comma emission. Tweak CRC wording.
> * src/abg-reporter-priv.h (maybe_report_diff_for_symbol):
> Return void.
> * tests/data/test-abidiff-exit/test-crc-report.txt: Shorten CRC
> wording.
> * tests/data/test-abidiff/test-crc-report.txt: Likewise.
> * tests/data/test-diff-filter/test-PR27569-report-0.txt:
> Likewise.
>
> Reviewed-by: Giuliano Procida <gprocida@google.com>
> Signed-off-by: Matthias Maennich <maennich@google.com>
Applied to master, thanks!
[...]
Cheers,
--
Dodji
prev parent reply other threads:[~2022-01-19 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 11:06 Matthias Maennich
2022-01-19 14:04 ` Dodji Seketeli [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=87fspjbz4e.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.com \
/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).