linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steve French <smfrench@gmail.com>
Cc: Dave Kleikamp <shaggy@kernel.org>,
	"Dr. David Alan Gilbert" <linux@treblig.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] smb3 client fixes
Date: Wed, 30 Aug 2023 21:21:31 -0700	[thread overview]
Message-ID: <CAHk-=wiCPoGieS-hkV+ze6UqvzNyPNT7WoD_v54ZuVwi-d5Bmw@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5mtpOtiP3Hk6FJPav8tYDhKJTQmELP31zYzVxf4DPNKbiQ@mail.gmail.com>

On Wed, 30 Aug 2023 at 13:48, Steve French <smfrench@gmail.com> wrote:
>
> - move UCS-2 conversion code to fs/nls and update cifs.ko and jfs.ko to use them

I've pulled this, but I think the new NLS_UCS2_UTILS config option
shouldn't be something that is asked about. The filesystems that want
it already select it, and users shouldn't be asked about a module with
no use.

The way to do that is to simply not have a user query string for it,
ie instead of

  config NLS_UCS2_UTILS
          tristate "NLS UCS-2 UTILS"

it could be (an dI think should be) just

  config NLS_UCS2_UTILS
          tristate

which tells the config system not to ask users about it.

Because users really shouldn't be asked questions that there is no point in.

And then, on a purely visual commentary about your pull request -
lines like these are just noise:

>  fs/{smb/server/uniupr.h => nls/nls_ucs2_utils.c} | 156
> +++++-------------------------------------
>  fs/nls/nls_ucs2_utils.h                          | 285
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

and the problem seems to be that you generate the diffstat in a very
wide terminal (where git tries to be helpful and give you lots of
detail), and then you cut-and-paste the result.

If you pipe it to a tool instead (xsel, perhaps), git will limit the
width of the diffstat to something sane.

Or, if you really want to use a terminal and cut-and-paste it
manually, you could try to tell git to use '--stat=72' to limit the
stat to 72 characters (which is the canonical "width for email", as
the Lord spake unto us all in rfc822, even if the Lord was confused
and also mentioned the number 65).

                         Linus

  reply	other threads:[~2023-08-31  4:22 UTC|newest]

Thread overview: 140+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 20:48 [GIT PULL] smb3 client fixes Steve French
2023-08-31  4:21 ` Linus Torvalds [this message]
2023-08-31  4:37   ` Steve French
2023-08-31 10:30   ` Dr. David Alan Gilbert
2023-08-31  4:30 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-04-13  9:18 Steve French
2024-04-13 17:12 ` pr-tracker-bot
2024-04-06  5:08 Steve French
2024-04-06 16:19 ` pr-tracker-bot
2024-03-29 17:05 Steve French
2024-03-29 19:27 ` pr-tracker-bot
2024-02-17  4:28 Steve French
2024-02-17 16:27 ` pr-tracker-bot
2024-02-10  0:33 Steve French
2024-02-10  1:15 ` pr-tracker-bot
2024-02-03 20:47 Steve French
2024-02-04  7:44 ` pr-tracker-bot
2024-01-26 22:25 Steve French
2024-01-27 17:21 ` pr-tracker-bot
2024-01-20 23:30 Steve French
2024-01-21  0:59 ` pr-tracker-bot
2024-01-10 22:26 Steve French
2024-01-11  2:24 ` pr-tracker-bot
2023-12-21  4:08 Steve French
2023-12-21  5:22 ` pr-tracker-bot
2023-12-08 22:26 Steve French
2023-12-09 20:34 ` pr-tracker-bot
2023-12-01 23:59 Steve French
2023-12-03  1:24 ` pr-tracker-bot
2023-11-18  0:37 Steve French
2023-11-18 19:44 ` pr-tracker-bot
2023-11-11 22:21 Steve French
2023-11-12  1:30 ` pr-tracker-bot
2023-10-15  2:15 Steve French
2023-10-15  2:47 ` pr-tracker-bot
2023-10-06 21:44 Steve French
2023-10-07 18:12 ` pr-tracker-bot
2023-09-23 17:28 Steve French
2023-09-23 19:08 ` pr-tracker-bot
2023-09-17  5:42 Steve French
2023-09-17 18:24 ` pr-tracker-bot
2023-09-10  1:36 Steve French
2023-09-10  3:17 ` pr-tracker-bot
2023-08-15 19:59 [GIT PULL] SMB3 " Steve French
2023-08-15 20:04 ` pr-tracker-bot
2023-07-29 19:07 [GIT PULL] smb3 " Steve French
2023-07-30  3:53 ` pr-tracker-bot
2023-07-16 14:59 Steve French
2023-07-16 19:58 ` pr-tracker-bot
2023-07-09  4:39 Steve French
2023-07-09 17:46 ` pr-tracker-bot
2023-07-01  4:20 Steve French
2023-07-01  5:04 ` pr-tracker-bot
2023-06-15  4:36 Steve French
2023-06-15 23:10 ` pr-tracker-bot
2023-05-21  4:52 Steve French
2023-05-21 18:09 ` pr-tracker-bot
2023-05-12 19:21 Steve French
2023-05-12 22:14 ` pr-tracker-bot
2023-05-06 20:45 Steve French
2023-05-07 18:12 ` pr-tracker-bot
2023-04-30 15:35 Steve French
2023-05-01 19:26 ` pr-tracker-bot
2023-04-22  2:43 Steve French
2023-04-22 16:47 ` pr-tracker-bot
2023-04-08 23:34 Steve French
2023-04-09  2:16 ` pr-tracker-bot
2023-04-01 21:32 Steve French
2023-04-02 18:02 ` pr-tracker-bot
2023-03-16 20:39 Steve French
2023-03-16 22:12 ` pr-tracker-bot
2023-03-03 23:29 Steve French
2023-03-04  0:39 ` pr-tracker-bot
2023-02-23  0:02 Steve French
2023-02-23  1:23 ` pr-tracker-bot
2023-01-20 21:23 Steve French
2023-01-20 22:38 ` pr-tracker-bot
2023-01-14  1:19 Steve French
2023-01-14 14:17 ` pr-tracker-bot
2022-12-20 21:49 Steve French
2022-12-21 18:50 ` pr-tracker-bot
2022-12-15 22:40 Steve French
2022-12-15 22:59 ` pr-tracker-bot
2022-11-27  4:44 [GIT PULL] SMB3 " Steve French
2022-11-27 17:14 ` pr-tracker-bot
2022-11-19  5:02 [GIT PULL] smb3 " Steve French
2022-11-19 17:14 ` pr-tracker-bot
2022-11-06  5:07 Steve French
2022-11-06 18:49 ` pr-tracker-bot
2022-10-30  2:40 Steve French
2022-10-30 18:34 ` pr-tracker-bot
2022-10-21 14:40 Steve French
2022-10-21 23:03 ` pr-tracker-bot
2022-10-16  0:33 Steve French
2022-10-16 18:18 ` pr-tracker-bot
2022-10-09  5:50 Steve French
2022-10-11  3:43 ` pr-tracker-bot
2022-09-16  5:25 Steve French
2022-09-16 14:21 ` pr-tracker-bot
2022-09-02  0:44 Steve French
2022-09-02 23:48 ` pr-tracker-bot
2022-08-27 21:43 Steve French
2022-08-28 18:18 ` pr-tracker-bot
2022-08-20 22:34 Steve French
2022-08-21 18:42 ` pr-tracker-bot
2022-08-13 21:44 Steve French
2022-08-14  0:39 ` pr-tracker-bot
2022-08-07  5:03 Steve French
2022-08-07 17:57 ` pr-tracker-bot
2022-07-14 18:41 Steve French
2022-07-14 20:42 ` pr-tracker-bot
2022-07-14  3:35 Steve French
2022-07-14 18:33 ` Linus Torvalds
2022-06-25 21:38 [GIT PULL] SMB3 " Steve French
2022-06-26 17:36 ` pr-tracker-bot
2022-06-18 22:38 Steve French
2022-06-19  3:02 ` pr-tracker-bot
2022-06-11 16:38 [GIT PULL] smb3 " Steve French
2022-06-12 18:40 ` pr-tracker-bot
2022-06-04 23:00 [GIT PULL] SMB3 " Steve French
2022-06-05  2:13 ` pr-tracker-bot
2022-05-27  6:52 Steve French
2022-05-27 16:31 ` Steve French
2022-04-22 17:00 [GIT PULL] smb3 " Steve French
2022-04-22 20:46 ` pr-tracker-bot
2022-04-14 20:42 Steve French
2022-04-14 23:25 ` pr-tracker-bot
2022-02-18  0:26 Steve French
2022-02-18 17:39 ` pr-tracker-bot
2022-02-12 20:20 Steve French
2022-02-13 18:04 ` pr-tracker-bot
2021-12-19  1:36 Steve French
2021-12-19 20:34 ` pr-tracker-bot
2021-12-04 20:41 Steve French
2021-12-04 21:50 ` pr-tracker-bot
2021-11-13 20:17 Steve French
2021-11-13 20:30 ` pr-tracker-bot
2021-09-11 17:23 Steve French
2021-09-12 17:11 ` Linus Torvalds
2021-09-12 18:41 ` pr-tracker-bot

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='CAHk-=wiCPoGieS-hkV+ze6UqvzNyPNT7WoD_v54ZuVwi-d5Bmw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=shaggy@kernel.org \
    --cc=smfrench@gmail.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;
as well as URLs for NNTP newsgroup(s).