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: CIFS <linux-cifs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: [GIT PULL] ksmbd fixes
Date: Thu, 9 Sep 2021 16:21:31 -0700	[thread overview]
Message-ID: <CAHk-=wiE8+=FvKk8nEdh62S_khLgoaasOo4kkwERaMK0u3GZqg@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5mvadF7FkC1NhVyYNBG_XzwH4daryt42YLJrHnn5ws1Y=A@mail.gmail.com>

On Thu, Sep 9, 2021 at 2:59 PM Steve French <smfrench@gmail.com> wrote:
>
> 18 ksmbd fixes including:

Sigh.. The text in the tag says 19.

But 18 was indeed correct.

For next time, if you're not quite certain, git can help you with these things:

   git rev-list --count --no-merges linus..

or similar.

But the important part is just the overview of what's actually going
on, not the number of patches. I tend to mostly edit that out anyway.

                Linus

  parent reply	other threads:[~2021-09-09 23:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 21:59 [GIT PULL] ksmbd fixes Steve French
2021-09-09 23:18 ` Steve French
2021-09-09 23:21 ` Linus Torvalds [this message]
2021-09-09 23:23 ` pr-tracker-bot
2021-10-09  4:59 Steve French
2021-10-09 22:05 ` pr-tracker-bot
2021-10-23 15:06 Steve French
2021-10-24 17:12 ` pr-tracker-bot
2021-11-12 16:19 Steve French
2021-11-13 19:44 ` pr-tracker-bot
2021-12-24  0:45 Steve French
2021-12-24  1:22 ` pr-tracker-bot
2022-01-20  6:14 Steve French
2022-01-20 11:59 ` pr-tracker-bot
2023-12-12  4:44 Steve French
2023-12-12 19:13 ` pr-tracker-bot
2024-05-08 15:19 Steve French
2024-05-08 17:46 ` 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-=wiE8+=FvKk8nEdh62S_khLgoaasOo4kkwERaMK0u3GZqg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.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).