From: raiz@firemail.cc
To: 9front@9front.org
Subject: Re: [9front] avoid infinite loop in upas/common mkfile
Date: Tue, 06 Jun 2017 23:39:00 +0000 [thread overview]
Message-ID: <257b22d2fe21ec7fbb643d7d34c8d63d@firemail.cc> (raw)
In-Reply-To: <10d11082eefc2412f0dbd362997c2063@firemail.cc>
On 2017-06-06 23:34, raiz@firemail.cc wrote:
> Running 'mk' from subdirectories of /sys/src/cmd/upas causes infinite
> loop because upas/common reruns mkupas which ends up in infinite loop.
>
> I attached a diff to fix it, correct me if I'm wrong.
>
> from postmaster@ur:
> The following attachment had content that we can't
> prove to be harmless. To avoid possible automatic
> execution, we changed the content headers.
> The original header was:
>
> Content-Transfer-Encoding: base64
> Content-Type: text/x-diff;
> name=upas_common_mkfile_fix.diff
> Content-Disposition: attachment;
> filename=upas_common_mkfile_fix.diff;
> size=266
sorry about that.
diff -r 9b0969c59d42 sys/src/cmd/upas/common/mkfile
--- a/sys/src/cmd/upas/common/mkfile Mon Jun 05 17:21:42 2017 +0200
+++ b/sys/src/cmd/upas/common/mkfile Wed Jun 07 02:30:49 2017 +0300
@@ -1,5 +1,4 @@
</$objtype/mkfile
-<../mkupas
LIB=libcommon.a$O
OFILES=\
next prev parent reply other threads:[~2017-06-06 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 23:34 raiz
2017-06-06 23:39 ` raiz [this message]
2017-06-07 5:58 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=257b22d2fe21ec7fbb643d7d34c8d63d@firemail.cc \
--to=raiz@firemail.cc \
--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).