It’s a commit that needs to be slightly different in master and 18.0, hence 2x
the # of commits.
Thanks for the 662cff8f pointer. Perfect example!
George
> On Feb 26, 2018, at 4:14 PM, Emil Velikov wrote:
>
> On 26 February 2018 at 20:18, Kyriazis, George
> wrote:
>> Thanks Jordan,
>>
>>
On 26 February 2018 at 20:18, Kyriazis, George
wrote:
> Thanks Jordan,
>
> 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?
>
When possible, please refrain from pushing to the stable branch.
If th
Thanks Jordan,
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?
George
> On Feb 23, 2018, at 5:43 PM, Justen, Jordan L
> wrote:
>
> On 2018-02-23 13:20:21, Kyriazis, George wrote:
>> Hello mesa-
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 neig
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 bes
