From: John Watts <contact@jookia.org>
To: barebox@lists.infradead.org
Subject: Re: Re: Draft of an errata for RFC916
Date: Thu, 26 Jan 2023 03:27:03 +1100 [thread overview]
Message-ID: <Y9FYVwlYP+iIQAsV@novena-choice-citizen> (raw)
In-Reply-To: <20230125151955.GB4155@tellis.lin.mbt.kalray.eu>
Hi Jules,
The looks good to me. Did you implement this in Barebox and test it?
John.
next prev parent reply other threads:[~2023-01-25 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:22 Question about RATP protocol limitation during handshake in barebox Jules Maselbas
2023-01-24 21:59 ` John Watts
2023-01-25 8:41 ` Jules Maselbas
2023-01-25 15:19 ` Draft of an errata for RFC916 Jules Maselbas
2023-01-25 16:27 ` John Watts [this message]
2023-01-25 17:11 ` Jules Maselbas
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=Y9FYVwlYP+iIQAsV@novena-choice-citizen \
--to=contact@jookia.org \
--cc=barebox@lists.infradead.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