From: ori@eigenstate.org
To: amavect@gmail.com, ori@eigenstate.org, 9front@9front.org
Subject: Re: [9front] replica mkfile patch
Date: Mon, 20 Jul 2020 18:59:50 -0700 [thread overview]
Message-ID: <E05B4BBA3714D62BDFDBF2998082DC15@eigenstate.org> (raw)
In-Reply-To: <0dc2ff9a-5f9e-33c2-fbfc-58a987a8ad02@gmail.com>
>> But we have no update binary. Anyone have
>> any idea what the goal of this rule was?
>
> If I remember, update was used to update the labs sources.
> Clearly long gone.
>
> Will this be committed soon?
>
> Thanks,
> Amavect
Yeah. I thought kvik was taking care of it, but since
he doesn't seem to have gotten to it yet, just did.
Thanks!
prev parent reply other threads:[~2020-07-21 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 3:06 Amavect
2020-07-19 3:40 ` [9front] " ori
2020-07-21 0:26 ` Amavect
2020-07-21 1:59 ` ori [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=E05B4BBA3714D62BDFDBF2998082DC15@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=amavect@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).