From: Dodji Seketeli <dodji@seketeli.org>
To: Giuliano Procida <gprocida@google.com>
Cc: libabigail@sourceware.org, kernel-team@android.com
Subject: Re: [PATCH 2/2] test-abidiff-exit.cc: Drop redundant --redundant.
Date: Tue, 07 Apr 2020 15:22:51 +0200 [thread overview]
Message-ID: <864ktvph04.fsf@seketeli.org> (raw)
In-Reply-To: <20200406084450.140975-2-gprocida@google.com> (Giuliano Procida's message of "Mon, 6 Apr 2020 09:44:50 +0100")
Giuliano Procida <gprocida@google.com> a écrit:
> * tests/test-abidiff-exit.cc: Drop obsolete --redundant flag
> and comment as --redundant is now implied by
> --leaf-changes-only.
Applied to master.
Thanks!
--
Dodji
next prev parent reply other threads:[~2020-04-07 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 8:44 [PATCH 1/2] Rename test-abidiff-exit/test-leaf[0-3] files Giuliano Procida
2020-04-06 8:44 ` [PATCH 2/2] test-abidiff-exit.cc: Drop redundant --redundant Giuliano Procida
2020-04-06 11:25 ` Matthias Maennich
2020-04-07 13:22 ` Dodji Seketeli [this message]
2020-04-06 11:24 ` [PATCH 1/2] Rename test-abidiff-exit/test-leaf[0-3] files Matthias Maennich
2020-04-07 13:22 ` 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=864ktvph04.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.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).