From: "B. Atticus Grobe" <grobe0ba@tcp80.org>
To: <9front@9front.org>
Subject: [9front] [PATCH] disk/mkext arg parsing
Date: Mon, 01 Aug 2022 12:08:14 -0500 [thread overview]
Message-ID: <CLUUVROF7MFY.2BTJ77AESFFG6@aphrodite.pulpie.local> (raw)
diff 30dcf55ee221b986aee6d428b4da431f6174c66b uncommitted
--- a/sys/src/cmd/disk/mkext.c
+++ b/sys/src/cmd/disk/mkext.c
@@ -39,7 +39,7 @@
namep = name;
ARGBEGIN{
case 'd':
- p = ARGF();
+ p = EARGF(usage());
if(strlen(p) >= LEN)
error("destination fs name too long\n");
strcpy(name, p);
reply other threads:[~2022-08-01 17:10 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=CLUUVROF7MFY.2BTJ77AESFFG6@aphrodite.pulpie.local \
--to=grobe0ba@tcp80.org \
--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).