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.