From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Error compiling libc/amd64/main9.s and/or main9p.s
Date: Wed, 27 Mar 2024 10:16:02 -0500 [thread overview]
Message-ID: <691efaa3-c195-4938-8a58-e76bc9a4eeaa@posixcafe.org> (raw)
In-Reply-To: <e8d39ff6-9d37-4248-a6db-203fb99b77ce@app.fastmail.com>
For what it's worth it's really not you being dumb, this is a flaw
in how we distribute information. Our information channels are well
detached from our update channels.
I think this is the 10th or so time someone has stumbled in to this,
so I am glad sl added it to the fqa.
We've discussed a solution to this a few times but nothing has stuck.
Let me give an idea then and we can find something that sticks.
Maybe /sys/lib/sysupdate (not attached to the path) could have a file
named after a commit with specific update instructions. Sysupdate
could then get the list of commits it is updating through, and cat
out those files from that directory.
Thanks,
moody
prev parent reply other threads:[~2024-03-27 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 16:37 Scott Flowers
2024-03-26 16:46 ` ori
2024-03-26 16:51 ` Jacob Moody
2024-03-26 17:15 ` Scott Flowers
2024-03-27 0:22 ` sl
2024-03-27 14:55 ` Scott Flowers
2024-03-27 15:16 ` Jacob Moody [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=691efaa3-c195-4938-8a58-e76bc9a4eeaa@posixcafe.org \
--to=moody@posixcafe.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).