From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] Patch cc to create .$O files with DMTMP
Date: Wed, 09 Jun 2021 02:24:04 +0200 [thread overview]
Message-ID: <0B00462D99BF898B2CA6C86FEB63B418@qak> (raw)
In-Reply-To: <YMADh7pYisdRmeo7@alice>
> Why do intermediate object files deserve special
> treatment?
When was the last time you went to pick up a
$O file from the dump?
next prev parent reply other threads:[~2021-06-09 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 1:08 Jacob Moody
2021-06-08 21:39 ` ori
2021-06-08 23:55 ` Anthony Martin
2021-06-09 0:24 ` kvik [this message]
2021-06-09 11:58 ` Jacob Moody
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=0B00462D99BF898B2CA6C86FEB63B418@qak \
--to=kvik@a-b.xyz \
--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).