From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] hgfs(4) loadrevinfo patch
Date: Sat, 7 Dec 2019 12:57:18 +1030 [thread overview]
Message-ID: <14C9554C3CB0AFFD0F8EDAA40E360768@musolino.id.au> (raw)
In-Reply-To: 82FE20F5BBA449C72E44DC98A38C3F73@felloff.net
> a good start, but why not just use Boffset() to get logoff/loglen?
Because Blength comes before Boffset in the man page.
> also, to find the "\n\n", just do a simple state machine:
Yeah, this becomes the obvious way when you use Boffset instead
of Blength; no need to keep track of all the bytes you're skipping.
I'll send an updated patch tomorrow night.
--
Cheers,
Alex Musolino
next reply other threads:[~2019-12-07 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 2:27 Alex Musolino [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-09 0:55 cinap_lenrek
2019-12-08 10:09 Alex Musolino
2019-12-07 2:10 cinap_lenrek
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=14C9554C3CB0AFFD0F8EDAA40E360768@musolino.id.au \
--to=alex@musolino.id.au \
--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).