From: atheik <atteh.mailbox@gmail.com>
To: jra@samba.org
Cc: atteh.mailbox@gmail.com, hyc.lee@gmail.com,
linkinjeon@kernel.org, linux-cifs@vger.kernel.org,
senozhatsky@chromium.org, smfrench@gmail.com, tom@talpey.com
Subject: Re: [PATCH 1/2] ksmbd: update documentation
Date: Thu, 1 Sep 2022 22:42:12 +0300 [thread overview]
Message-ID: <20220901194212.28441-1-atteh.mailbox@gmail.com> (raw)
In-Reply-To: <YxD6SEN9/3rEWaNR@jeremy-acer>
On Thu, 1 Sep 2022 11:30:32 -0700, Jeremy Allison wrote:
>
>Samba adds and or changes functionality in smb.conf all
>the time, without coordination with ksmbd. If you call
>your config file smb.conf then we would have to coordinate
>with you before any changes.
ksmbd-tools has always called its config file `smb.conf'. Has this
matter come up before? I don't have anything against changing the name,
but I'd be surprised if my writing of the man pages first prompted this
concern.
>
>Over time, the meaning/use/names of parameters will drift
>apart leading to possible conflicts.
>
>Plus it leads to massive user confusion (am I running
>smbd or ksmbd ? How do I tell ? etc.).
>
>It is simple hygene to keep these names separate.
>
>Please do so.
Atte Heikkilä
next prev parent reply other threads:[~2022-09-01 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 14:17 [PATCH 1/2] ksmbd: update documentation Namjae Jeon
2022-08-30 14:17 ` [PATCH 2/2] ksmbd: remove generic_fillattr use in smb2_open() Namjae Jeon
2022-09-01 6:08 ` Hyunchul Lee
2022-08-30 16:13 ` [PATCH 1/2] ksmbd: update documentation Tom Talpey
2022-08-31 1:36 ` Namjae Jeon
2022-09-01 5:19 ` atheik
2022-09-01 13:06 ` Tom Talpey
2022-09-01 16:14 ` Jeremy Allison
2022-09-01 17:41 ` atheik
2022-09-01 18:30 ` Jeremy Allison
2022-09-01 18:52 ` Tom Talpey
2022-09-01 22:24 ` Steve French
2022-09-01 23:54 ` Tom Talpey
2022-09-01 19:42 ` atheik [this message]
2022-09-01 20:26 ` Jeremy Allison
2022-09-01 21:21 ` ronnie sahlberg
2022-09-01 21:37 ` Steve French
2022-09-01 21:48 ` Jeremy Allison
2022-09-02 0:56 ` Namjae Jeon
2022-09-02 2:11 ` Jeremy Allison
2022-09-02 12:35 ` Tom Talpey
2022-09-02 13:33 ` Namjae Jeon
2022-08-30 17:32 ` Tom Talpey
2022-08-31 0:02 ` Namjae Jeon
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=20220901194212.28441-1-atteh.mailbox@gmail.com \
--to=atteh.mailbox@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=jra@samba.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.com \
/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