From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] Beware of 'mk nuke': mkrunetype.c
Date: Wed, 29 Mar 2023 13:19:32 -0700 [thread overview]
Message-ID: <20D239A642C9E9657FE23CE8E26549A9@smtp.pobox.com> (raw)
In-Reply-To: <69f9ac13-6555-4ecf-7fa6-630739018ace@posixcafe.org>
Quoth Jacob Moody <moody@mail.posixcafe.org>:
> I have modified the rules so that no automatic generation of these
> files will be done, moving them to an explicit virtual rule. This
> should prevent this happening in the future to anyone else.
>
> For records this commit is:
> 997ea3e5ccd9cba5d1f8fad48a0320574696f5bc
>
> Thank you again for your bug report,
> moody
>
Confirmed, nuke'ing now doesn't exhibit the same behavior, and the
system builds. Thanks, moody!
prev parent reply other threads:[~2023-03-29 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 7:24 Romano
2023-03-29 7:29 ` Jacob Moody
2023-03-29 14:41 ` unobe
2023-03-29 15:16 ` Jacob Moody
2023-03-29 18:53 ` Jacob Moody
2023-03-29 20:19 ` unobe [this message]
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=20D239A642C9E9657FE23CE8E26549A9@smtp.pobox.com \
--to=unobe@cpan.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).