From: binary cat <dogedoge61@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] /proc/n/fd format clarification
Date: Wed, 9 Jun 2021 17:24:01 -0400 [thread overview]
Message-ID: <CAHtSCHJ7N_O4QEJAAUgug=LJr0QS_aryrx5Yrhb0Wi=ZdZASEA@mail.gmail.com> (raw)
In-Reply-To: <YL6vzQ1lwrM7/xQX@alice>
>Assuming something that isn't actually written down in
>the documentation is not a good idea.
The problem is that the actual format of the qid is undocumented (as
far as I can tell).
This is what I mean about the documentation being clearer.
>This still wouldn't work since the third field, the type, is a
>single UTF-8 encoded Unicode rune which is not a fixed width.
Well, it is not impossible to pad that with a non-printable ascii character,
but now you are possibly actually breaking stuff.
Seems like it would be best to add a few lines to the documentation,
and leave it at that.
– binarycat
prev parent reply other threads:[~2021-06-09 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 13:26 binary cat
2021-06-05 21:04 ` [9front] " Anthony Martin
2021-06-05 21:58 ` [9front] " nicolagi
2021-06-07 17:16 ` binary cat
2021-06-07 23:37 ` ori
2021-06-07 23:46 ` Anthony Martin
2021-06-09 21:24 ` binary cat [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='CAHtSCHJ7N_O4QEJAAUgug=LJr0QS_aryrx5Yrhb0Wi=ZdZASEA@mail.gmail.com' \
--to=dogedoge61@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).