On Thu, Oct 17, 2019 at 12:22:18PM +0200, Han-Wen Nienhuys wrote:
> On Wed, Oct 16, 2019 at 9:09 PM Mark Brown <broonie@kernel.org> wrote:
> > On Wed, Oct 16, 2019 at 08:56:53PM +0200, Han-Wen Nienhuys wrote:

> > > With the email workflow, isn't it hard to keep track of which patch
> > > went into which tree? Something that tracks the identity of commit
> > > (like Change-Id) as it travels across trees could help here.

> > Once something's in git it flows into other trees via merges so the
> > commit ID is stable, the exception is backports where the ID from
> > mainline gets referenced in the backport.  Normal development doesn't
> > use cherry picks really.

> Right, so once it's in Git, the review story is done, and everything
> we've discussed so far is really only about what happens before the
> merging?

*Mostly* - pull requests do get reviewed and may need to be rebuilt but
pretty much.  It's certainly an out of normal workflow.