[Automated-testing] Structured feeds
Tim.Bird at sony.com
Tim.Bird at sony.com
Thu Nov 7 00:48:19 PST 2019
> -----Original Message-----
> From: Dmitry Vyukov
>
> This is another follow up after Lyon meetings. The main discussion was
> mainly around email process (attestation, archival, etc):
> https://lore.kernel.org/workflows/20191030032141.6f06c00e@lwn.net/T/#t
>
> I think providing info in a structured form is the key for allowing
> building more tooling and automation at a reasonable price. So I
> discussed with CI/Gerrit people and Konstantin how the structured
> information can fit into the current "feeds model" and what would be
> the next steps for bringing it to life.
>
> Here is the outline of the idea.
> The current public inbox format is a git repo with refs/heads/master
> that contains a single file "m" in RFC822 format. We add
> refs/heads/json with a single file "j" that contains structured data
> in JSON format. 2 separate branches b/c some clients may want to fetch
> just one of them.
Can you provide some idea (maybe a few examples) of the types of
structured data that would be in the json branch?
-- Tim
More information about the automated-testing
mailing list