[Ksummit-discuss] [MAINTAINER SUMMIT] Distribution kernel bugzillas considered harmful

[Jiri Kosina]

On Wed, 5 Sep 2018, James Bottomley wrote:

> > We are drifting away a bit here, but now that you have mentioned it,
> > let me add a datapoint to this -- it's actually causing issues to
> > our workflow, as we have scsi.git as one of the upstreams [1], and
> > when you rebase, it blows up our git workflow and we have to fixup
> > things manually.
> 
> Describe the issues and we'll try to come up with a fix, but on the
> whole you should regard the scsi trees somewhat similarly to linux-
> next: it's our proposal for a patch set but we may update it.

We order patches in our trees in the same git-topological-ordering as they 
are upstream. It has a lot of benefits, most importantly: it doesn't 
introduce artificial conflicts that don't exist in reality.

In order to achieve that, we of course need 1:1 mapping between our 
patches and upstream commits.
Rebases destroy that mapping.

And in some areas (scsi is one, but not the only one), we basically had no 
other choice than considering maintainer's tree to be already "upstream 
enough", without waiting for Linus' tree merge.

> > So if you are aware of your tree having downstreams, and care about
> > not breaking them and want to be nice to them, you shouldn't rebase
> > that tree [2].
> 
> Well, I wasn't aware of this one, but I'm sure we can come up with a
> functional workflow once I understand what's happening with the
> downstream tree.

Thanks,

-- 
Jiri Kosina
SUSE Labs