From: james palmer <james@biobuf.link>
To: 9front@9front.org
Subject: [9front] aout2uimage patch
Date: Tue, 22 Dec 2020 16:56:28 +0000 [thread overview]
Message-ID: <B34487832DEC87C5C09EADE93E2DC75C@biobuf.link> (raw)
just a small typo,
the usage() function is missing a newline in the call to fprint():
diff -r 1ae20c21a286 sys/src/cmd/aux/aout2uimage.c
--- a/sys/src/cmd/aux/aout2uimage.c Sat Dec 19 19:15:02 2020 +0100
+++ b/sys/src/cmd/aux/aout2uimage.c Tue Dec 22 16:52:30 2020 +0000
@@ -67,7 +67,7 @@
void
usage(void)
{
- fprint(2, "usage: %s a.out", argv0);
+ fprint(2, "usage: %s a.out\n", argv0);
exits("usage");
}
next reply other threads:[~2020-12-22 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 16:56 james palmer [this message]
2020-12-22 18:34 ` cinap_lenrek
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=B34487832DEC87C5C09EADE93E2DC75C@biobuf.link \
--to=james@biobuf.link \
--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).