From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] tinc(8) protocol now at 1.0.36?
Date: Sun, 15 Aug 2021 12:01:00 +0200 [thread overview]
Message-ID: <8DBEB4A51F83C368FDB68928D3A91C46@felloff.net> (raw)
In-Reply-To: <148FA590AEF1CB246DB367302A906D39@smtp.pobox.com>
thanks for the review!
> cinap is the only one who has committed changes to tinc(8). So maybe
> this is really a question for cinap: can 9front's version be
> advertised as supporting 1.0.36?
yes, that is fine. it is good to check if we made similar implementation
mistakes as the original tinc. even tho our implementation is completely
independent and doesnt use any of the original tinc code.
the protocol is actually 1.0, as described in the technical information.
there is also a 1.1 protocol, that is not implemented by us.
thanks for fixing the spelling errors, i have applied your patch.
--
cinap
prev parent reply other threads:[~2021-08-15 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 7:22 unobe
2021-08-15 10:01 ` cinap_lenrek [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=8DBEB4A51F83C368FDB68928D3A91C46@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).