| === himcesjf_ is now known as him-cesjf | ||
| === Alives_ is now known as Alives | ||
| === DalekSec_ is now known as DalekSec | ||
| === cjwatson_ is now known as cjwatson | ||
| Moral_ | I am a kernel dev at Intel. We want to cherry pick a commit staged for 4.16 into the Bionic tree and submit it. We know the freeze date is coming up quick. 2 Questions: 1. Are we allowed to even cherry pick non-security stuff out of a release that's in RC? 2. I assume the process for submitting our pathc is documented somewhere on the wiki? (slowly picking through it) | 16:55 |
|---|---|---|
| TJ- | apw *** | 16:56 |
| cascardo | Moral_: first, you need to open a bug, that bug must be present in the commit message | 17:02 |
| cascardo | I am not sure there is some updated documentation about that, but you can look at other messages in the mailing list | 17:03 |
| Moral_ | ok I will take a look, thx. | 17:04 |
| cascardo | if it's on linus' tree already, on an RC, just use cherry-pick -x to add the upstream commit information | 17:05 |
| cascardo | if you needed to fix any conflicts, or change the original commit in some other way, change "cherry picked from" to "backported from" | 17:06 |
| cascardo | and indicate in the subject header (between brackets) the series you are targeting, like [Bionic PATCH], for example | 17:06 |
| cascardo | Moral_: hope that helps. look for the BugLink lines on other messages | 17:07 |
| Moral_ | Yeah, that was helpful. Gonna test then submit something here soon. | 17:09 |
| === acheronuk_ is now known as acheronuk | ||
| === zyga_ is now known as zyga | ||
| === keithzg_ is now known as keithzg | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!