From: Nick Desaulniers <ndesaulniers@google.com>
To: "# 3.4.x" <stable@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: clang-built-linux <clang-built-linux@googlegroups.com>
Subject: commit <sha> upstream. vs git cherry-pick -x
Date: Wed, 10 Mar 2021 14:37:03 -0800 [thread overview]
Message-ID: <CAKwvOdmAEKQmi-Hy4Gi33t4nb3mCuKUd_qmbEdwrkRwezAWpiA@mail.gmail.com> (raw)
Hello stable maintainers,
While working on some backports I'm about to send hopefully today or
tomorrow, I was curious why the convention seems to be for folks to
use "commit <sha> upstream." in commit messages? I know that's what's
in https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-3,
but I was curious whether the format from `git cherry-pick -xs <sha>`
is not acceptable? I assume there's context as to why not? It is nice
to have that info uniformly near the top, but I find myself having to
cherry-pick then amend a lot. Or is there an option in git to
automate the stable kernel's preferred style?
--
Thanks,
~Nick Desaulniers
next reply other threads:[~2021-03-10 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 22:37 Nick Desaulniers [this message]
2021-03-10 23:35 ` commit <sha> upstream. vs git cherry-pick -x Sasha Levin
2021-03-11 7:00 ` 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=CAKwvOdmAEKQmi-Hy4Gi33t4nb3mCuKUd_qmbEdwrkRwezAWpiA@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--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.