From: hiro <23hiro@gmail.com>
Cc: 9front@9front.org
Subject: Re: [9fans] Re: [9front] dropped emails
Date: Tue, 26 Jan 2021 12:47:32 +0100 [thread overview]
Message-ID: <CAFSF3XO5GxUPTd8_=hO4y3TCFWspFCrFOjGhWydcDGtK-bd4uQ@mail.gmail.com> (raw)
In-Reply-To: <6E86F4DB7671E5DEEC00495E24A14B3F@eigenstate.org>
sorry, didn't realize the 9fans in there, sending again to 9front:
Sun, Jan 24, 2021 at 4:09 AM (Delivered after 78941 seconds)
Mon, Jan 25, 2021 at 12:50 PM (Delivered after 85498 seconds)
slowly stuff is finally getting through...
On 1/25/21, ori@eigenstate.org <ori@eigenstate.org> wrote:
> Quoth ori@eigenstate.org:
>> Quoth Lyndon Nerenberg <lyndon@orthanc.ca>:
>> > hiro writes:
>> > > only found out by accident,
>> >
>> > Not sure what's going on. I sent a couple of messages to
>> > 9front and 9front-bugs yesterday that vanished into a black
>> > hole ...
>> >
>> > --lyndon
>>
>> As far as we can tell, they're currently in
>> the queue, which is currently running at a
>> crawl -- we're aware of the problem, and are
>> poking at upas to figure out what's up.
>
> As far as we know, the mails directed at
> working addresses should be sent now.
>
> We're now running a hacked version of
> runq that should be processing messages
> in parallel, but without clobbering
> the system with load.
>
> In case of mailing list flakiness, please
> complain -- and put me in the cc list.
>
> If you do not get this message, please
> report it at once.
>
>
> ------------------------------------------
> 9fans: 9fans
> Permalink:
> https://9fans.topicbox.com/groups/9fans/T75f937755279e2c1-M0895c0835dc165995d228528
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>
next prev parent reply other threads:[~2021-01-26 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 14:41 hiro
2021-01-24 20:56 ` Lyndon Nerenberg
2021-01-24 21:16 ` [9fans] " ori
2021-01-25 4:45 ` ori
2021-01-26 11:47 ` hiro [this message]
2021-01-25 0:52 ` Stanley Lieber
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='CAFSF3XO5GxUPTd8_=hO4y3TCFWspFCrFOjGhWydcDGtK-bd4uQ@mail.gmail.com' \
--to=23hiro@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).