From: Tom de Vries <tdevries@suse.de>
To: dwz@sourceware.org, jakub@redhat.com
Subject: [committed] Add missing --devel-dump-dups in usage
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <20200124105055.GA24224@delia> (raw)
Hi,
Committed to trunk.
Thanks,
- Tom
Add missing --devel-dump-dups in usage
2020-01-24 Tom de Vries <tdevries@suse.de>
* dwz.c (usage): Add --devel-dump-dups.
---
dwz.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/dwz.c b/dwz.c
index e98310b..b12645d 100644
--- a/dwz.c
+++ b/dwz.c
@@ -14706,6 +14706,7 @@ usage (void)
" --devel-save-temps\n"
" --devel-dump-dies\n"
" --devel-dump-dups\n"
+ " --devel-dump-pus\n"
" --devel-unoptimized-multifile\n"
" --devel-verify-dups\n"
" --devel-verify-edges\n"
reply other threads:[~2020-01-24 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200124105055.GA24224@delia \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.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).