From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] mklib, upas/common: clean up libcommon properly
Date: Wed, 03 Feb 2021 08:49:00 -0600 [thread overview]
Message-ID: <EB794C5E-D372-43BE-91BC-4E69EAB5291D@gmail.com> (raw)
In-Reply-To: <20210202201459.GA79537@serv.nsmprlab>
rc doesn't expand regexp inside variables, which was my mistake.
Changeset 8293 seems to indicate that we want to clean the local libs, while nuke is for removing the syslibs. So, I think this is a good patch.
For completeness, we should also remove the CLEANFILES from other local lib mkfiles.
Thanks,
Amavect
prev parent reply other threads:[~2021-02-03 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 20:14 mikan
2021-02-03 14:49 ` Amavect [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=EB794C5E-D372-43BE-91BC-4E69EAB5291D@gmail.com \
--to=amavect@gmail.com \
--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).