[Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance

Josh Triplett josh at joshtriplett.org
Tue Sep 11 01:14:12 UTC 2018


On Tue, Sep 11, 2018 at 01:16:18AM +0200, Daniel Vetter wrote:
> On Mon, Sep 10, 2018 at 11:30 PM, Josh Triplett <josh at joshtriplett.org> wrote:
> > On Mon, Sep 10, 2018 at 10:59:26PM +0300, Laurent Pinchart wrote:
> >> One of the issues here is that patch series don't have fixed boundaries over
> >> their lifetime, the same way patches don't. A patch can evolve in scope from
> >> version to version, and similarly so can a patch series. It's not uncommon for
> >> patches to be dropped or added and for series to be split or merged. I've in
> >> the past incorporated part of an RFC patch series in the v1 of a series with a
> >> larger scope (after discussing it with the original developer of course).
> >
> > I do have some tools and algorithms that could be adapted to help
> > cross-match patch series and show how they evolve over time. It isn't
> > that hard to detect patch reordering and show interdiffs between
> > corresponding patches. Extending that to match patches between series
> > isn't much harder.
> 
> Is that built on top of the new git range-diff tool, or at least that
> concept? Or something else?

Same concept, just a different implementation of an algorithm comparable
to tbdiff's.


More information about the Ksummit-discuss mailing list