From: Greg KH <gregkh@linuxfoundation.org>
To: "Protopopov, Boris" <pboris@amazon.com>
Cc: stable <stable@vger.kernel.org>
Subject: Re: [PATCH 4.9-5.8] Convert trailing spaces and periods in path components
Date: Mon, 19 Oct 2020 19:43:25 +0200 [thread overview]
Message-ID: <20201019174325.GD3327376@kroah.com> (raw)
In-Reply-To: <B1901644-CAEB-45B7-87F8-A05C70423914@amazon.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Mon, Oct 19, 2020 at 02:17:35PM +0000, Protopopov, Boris wrote:
> I could not find the patch in Linus's tree at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/cifs/cifs_unicode.c#n491 or in the commit list. The patch is in linux-next, commit https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7698a46ed868f03afe1871d7cb63061db6a62b71
Have you read the rules for stable patches:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Please do so, you seem to be missing the "MUST BE IN LINUS'S TREE"
requirement...
greg k-h
next prev parent reply other threads:[~2020-10-19 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 15:28 [PATCH 4.9-5.8] Convert trailing spaces and periods in path components Boris Protopopov
2020-10-18 5:55 ` Greg KH
2020-10-19 14:17 ` Protopopov, Boris
2020-10-19 17:43 ` Greg KH [this message]
2020-10-19 18:10 ` Protopopov, Boris
-- strict thread matches above, loose matches on Subject: below --
2020-10-16 19:22 Boris Protopopov
2020-10-17 6:20 ` Greg KH
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=20201019174325.GD3327376@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=pboris@amazon.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.