From: Kristoffer Haugsbakk Date: Thu, 05 Feb 2026 16:19:12 GMT Subject: Re: [PATCH 4/4] trace2: emit cmd_ancestry data for Windows Message-ID: <8775e4d7-4793-413d-a0ff-c1d325ed04e5@app.fastmail.com> In-Reply-To: On Thu, Feb 5, 2026, at 17:05, Matthew John Cheetham via GitGitGadget wrote: > From: Matthew John Cheetham > > Since 2f732bf1 (tr2: log parent process name) it is now possible to emit The usual way to refer to commits is to use `git show -s --pretty=reference`. (Or maybe with `--abbrev=8` as well which seems to be the case here.) That also adds the date. See `SubmittingPatches`. > a specific process ancestry event in TRACE2. We should emit the Windows > process ancestry data with the correct event type. > > To not break existing consumers of the data_json "windows/ancestry" > event, we continue to emit the ancestry data as a JSON event. > > Signed-off-by: Matthew John Cheetham > --- >[snip]