From: BurnZeZ@feline.systems
To: 9front@9front.org
Subject: Re: [9front] Latest 9pcf crashes on boot
Date: Mon, 16 May 2016 00:49:14 -0400 [thread overview]
Message-ID: <545b5528ddf80f84bc73b7632385961a@meiling.znet> (raw)
In-Reply-To: <D618A796-D260-4CA4-9E0A-29587ED02863@stanleylieber.com>
> Here it is again (mailed, again, from a phone).
I manually processed the SMTP transactions to ensure nupas wasn't
breaking things. The SMTP header says it's sending so many bytes, but
it doesn't sync up with what was actually sent.
Header: 1577126
File 1: 1551654 (25472 bytes short)
File 2: 1551369 (285 bytes shorter)
I opened them in jpg after cinap's latest commit, and can see a valid
portion of the image from file 1 is missing from file 2.
The phone's hull has been breached and bytes are escaping into space.
next prev parent reply other threads:[~2016-05-16 4:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 1:57 sl
2016-05-16 2:03 ` BurnZeZ
2016-05-16 2:10 ` sl
2016-05-16 2:32 ` BurnZeZ
2016-05-16 2:39 ` stanley lieber
2016-05-16 4:49 ` BurnZeZ [this message]
2016-05-16 15:03 ` stanley lieber
2016-05-16 3:19 ` kokamoto
2016-05-16 3:41 ` cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2016-05-15 19:39 stanley lieber
2016-05-16 0:24 ` [9front] " kokamoto
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=545b5528ddf80f84bc73b7632385961a@meiling.znet \
--to=burnzez@feline.systems \
--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).