[Mesa-dev] Patch submit question
george.kyriazis at intel.com
Mon Feb 26 20:18:17 UTC 2018
Since I won’t be checking this in to mesa master, what do I need to do to actually push it to the stable branch, after I get a review on mesa-dev?
> On Feb 23, 2018, at 5:43 PM, Justen, Jordan L <jordan.l.justen at intel.com> wrote:
> On 2018-02-23 13:20:21, Kyriazis, George wrote:
>> Hello mesa-dev,
>> I have a quick patch submission question:
>> I have a patch that I’d like to also nominate to mesa-stable
>> (specifically 18.0.1 or 18.0.2), however the same patch is different
>> between master and stable branches, due to neighboring code having
>> changed in the meantime.
>> What’s the best process of submitting / pushing this sort of change?
> 719f2c934030f74ce0a4892233f494f168852698 was an 18.0 specific patch. I
> Cc'd 18.0 in the commit message:
> Cc: "18.0" <mesa-stable at lists.freedesktop.org>
> And, I used:
> git format-patch --subject-prefix=PATCH\ 18.0
> You might also add "Fixes" to the commit message if applicable, even
> though in this case it wouldn't be used to trigger cherry-picking to
> the stable branch.
More information about the mesa-dev