From: "Roberto E. Vargas Caballero" <k0ga@shike2.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH 2/6] cifsd: clarify SMBv1 is supported, not SMB 2/3.
Date: Fri, 15 Dec 2023 01:01:34 +0100 [thread overview]
Message-ID: <ZXuXXvrF0X7xHi/+@simple-cc.openbsd.amsterdam> (raw)
In-Reply-To: <B4B6A72254459CDC5608E9F0252F87BF@smtp.pobox.com>
Hi,
Cinap dis you see these commits? I think they seem interesting, but you should take
a look since you know more than me about this topic.
Regards,
next prev parent reply other threads:[~2023-12-15 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 6:34 Romano
2023-09-28 7:14 ` unobe
2023-12-11 18:57 ` unobe
2023-12-11 19:31 ` unobe
2023-12-15 0:01 ` Roberto E. Vargas Caballero [this message]
2023-12-18 12:41 ` cinap_lenrek
2023-12-18 18:05 ` cinap_lenrek
2023-12-18 18:55 ` unobe
2023-12-19 17:36 ` 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=ZXuXXvrF0X7xHi/+@simple-cc.openbsd.amsterdam \
--to=k0ga@shike2.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).