From: tangmeng <tangmeng@uniontech.com>
To: libabigail@sourceware.org
Cc: tangmeng <tangmeng@uniontech.com>
Subject: [libabigail][PATCH v2] Fix trivial typo when printing help information
Date: Wed, 27 Oct 2021 11:44:24 +0800 [thread overview]
Message-ID: <20211027034424.29705-1-tangmeng@uniontech.com> (raw)
When abicompat prints its help information, it does not terminate
it with a newline and option format is not aligned the way that
other commands do.
Signed-off-by: tangmeng <tangmeng@uniontech.com>
---
tools/abicompat.cc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tools/abicompat.cc b/tools/abicompat.cc
index be3946e1..60cd794f 100644
--- a/tools/abicompat.cc
+++ b/tools/abicompat.cc
@@ -105,12 +105,12 @@ display_usage(const string& prog_name, ostream& out)
"to the debug information directory for the first library\n"
<< " --lib-debug-info-dir2|--libd2 <path-to-lib-debug-info2> set the path "
"to the debug information directory for the second library\n"
- << "--suppressions|--suppr <path> specify a suppression file\n"
- << "--no-redundant do not display redundant changes\n"
- << "--no-show-locs do now show location information\n"
- << "--redundant display redundant changes (this is the default)\n"
- << "--weak-mode check compatibility between the application and "
- "just one version of the library."
+ << " --suppressions|--suppr <path> specify a suppression file\n"
+ << " --no-redundant do not display redundant changes\n"
+ << " --no-show-locs do now show location information\n"
+ << " --redundant display redundant changes (this is the default)\n"
+ << " --weak-mode check compatibility between the application and "
+ "just one version of the library.\n"
;
}
--
2.20.1
next reply other threads:[~2021-10-27 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 3:44 tangmeng [this message]
2021-10-27 10:52 ` 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=20211027034424.29705-1-tangmeng@uniontech.com \
--to=tangmeng@uniontech.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).