From: "Benjamin Purcell" <spew@cbza.org>
To: 9front@9front.org
Subject: Re: [9front] upas/fs lstk(), one more time
Date: Sat, 30 Sep 2023 19:51:25 -0600 [thread overview]
Message-ID: <c9b8b14d-8c76-407c-880c-7e2aa6b48bbf@app.fastmail.com> (raw)
In-Reply-To: <DDF801119CF0AF7FA40847F2C54A7614@gaff.inri.net>
The suspense is killing me.
On Sat, 30 Sep 2023, at 18:35 UTC-06:00, sl@stanleylieber.com wrote:
> i backed up my mbox and added messages back in batches, checking after
> each batch that upas/fs was still able to open it. i did this until i
> found a specific message upas/fs choked on.
>
> sl
next prev parent reply other threads:[~2023-10-01 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 21:38 sl
2023-10-01 0:35 ` sl
2023-10-01 1:51 ` Benjamin Purcell [this message]
2023-10-01 4:13 ` ori
2023-10-01 4:20 ` Stanley Lieber
2023-10-01 9:32 ` hiro
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=c9b8b14d-8c76-407c-880c-7e2aa6b48bbf@app.fastmail.com \
--to=spew@cbza.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).