The intention of commit '663e7293e042 ("qf: Allow rebase
function to start from anywhere.")' was to allow the
qf rebase to start from anywhere, including from a place
where not patch is yet applied with quilt.
However pop -f was not the right answer for that.
We need to make sure that qf pull pro
qf_checkout implies that you need to have that baseline
on your local repository, what it is not good for a distributed
maintenance.
Let's make qf pull -f useful for the case we want to start
a clean rebase from anywhere.
v2: Remove dubious comments and use -f.
Cc: Paulo Zanoni
Cc: Michel Thier
When working with wiggle to easily solve rebasing
conflicts we also need to be able to easily continue,
easily see the impacted files and easily clean the
repo to avoid ending up with many .rej and .porig files.
v2: Remove -r from rm. (Lucas)
Use -z instead of '== ""' comparison. (Lucas)
A
Hi Dave,
Fixes for 2 regressions that got captured by CI.
Here goes drm-intel-fixes-2018-03-07:
- 2 fixes: 1 for perf and 1 execlist submission race.
Thanks,
Rodrigo.
The following changes since commit 661e50bc853209e41a5c14a290ca4decc43cbfd1:
Linux 4.16-rc4 (2018-03-04 14:54:11 -0800)
are
Hi Dave,
Only a few sun4i fixes this week. Please pull.
Regards,
Gustavo
drm-misc-fixes-2018-03-07:
sun4i fixes on clk, division by zero and LVDS.
The following changes since commit 9a191b114906457c4b2494c474f58ae4142d4e67:
virtio-gpu: fix ioctl and expose the fixed status to userspace. (201
On Tue, Mar 6, 2018 at 8:20 PM, Sean Paul wrote:
> On Tue, Mar 06, 2018 at 09:07:52PM +0200, Ville Syrjälä wrote:
>> On Tue, Mar 06, 2018 at 02:01:21PM -0500, Sean Paul wrote:
>> > On Tue, Mar 06, 2018 at 07:42:53AM +0100, Daniel Vetter wrote:
>> > > On Tue, Mar 6, 2018 at 12:20 AM, Sean Paul wro
