commit <sha> upstream. vs git cherry-pick -x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux