From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: Sean Hinchee <henesy.dev@gmail.com>
Cc: 9front@9front.org
Subject: Re: [9front] Re: Update system: Difference "mk nuke" and "mk clean"?
Date: Thu, 21 Apr 2022 20:02:21 +0200 [thread overview]
Message-ID: <871qxqe2mq.fsf@turtle-trading.net> (raw)
In-Reply-To: <CADmmOS8kFTCuVRuT7Mtq7eA_iOOAqz8K_bC9ELqx5O=XFRzaCQ@mail.gmail.com> (Sean Hinchee's message of "Thu, 21 Apr 2022 01:51:09 -0700")
Sean Hinchee writes:
> As sirjofri states, nuke will delete library targets and more files
> than clean will.
Ok, deleting libraries makes sense. So "mk clean" is opposite to "mk
all", and "mk nuke" goes with "mk install". Within reason, I guess, as
deleting programs would not make sense ever.
Thanks, benny
prev parent reply other threads:[~2022-04-21 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 17:41 [9front] " Benjamin Riefenstahl
2022-04-20 15:44 ` [9front] " Benjamin Riefenstahl
2022-04-20 17:05 ` sirjofri
2022-04-21 8:51 ` Sean Hinchee
2022-04-21 18:02 ` Benjamin Riefenstahl [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=871qxqe2mq.fsf@turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--cc=9front@9front.org \
--cc=henesy.dev@gmail.com \
/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).