From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Subject: [9front] [PATCH] diff: include -u in usage()
Date: Thu, 13 Oct 2022 01:49:09 +0330 [thread overview]
Message-ID: <ce0e9d0f-c704-8e6b-3ea0-319a3356f965@riseup.net> (raw)
adds -u in usage()
--- /sys/src/cmd/diff/main.c
+++ /sys/src/cmd/diff/main.c
@@ -176,7 +176,7 @@
void
usage(void)
{
- fprint(2, "usage: %s [-abcefmnrw] file1 ... file2\n", argv0);
+ fprint(2, "usage: %s [-abcefmnruw] file1 ... file2\n", argv0);
exits("usage");
}
reply other threads:[~2022-10-12 22:20 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=ce0e9d0f-c704-8e6b-3ea0-319a3356f965@riseup.net \
--to=mkf9@riseup.net \
--cc=9front@9front.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 NNTP newsgroup(s).