Re: [Xen-devel] [OSSTEST PATCH 4/5] Emails: Provide X-Osstest-Versions-This and That headers

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Tue, 2015-06-30 at 14:49 +0100, Ian Jackson wrote:
> Specifically:
>  * Provide headerprint() in sg-report-flight
>  * Use it to add X-Osstest-Versions headers based on %specver
>  * Cause cr-daily-branch to always enable the feature
>  * Document this in README.email
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
> ---
>  README.email     |   14 ++++++++++++++
>  cr-daily-branch  |    2 +-
>  sg-report-flight |   10 ++++++++++
>  3 files changed, 25 insertions(+), 1 deletion(-)
> 
> diff --git a/README.email b/README.email
> index 3f95fa8..be79f88 100644
> --- a/README.email
> +++ b/README.email
> @@ -104,3 +104,17 @@ history.  Here are some examples:
>  The flight numbers quoted in these step failure summaries may
>  sometimes be suffixed with `-bisect' to show that the indicated flight
>  was part of a bisection attempt, rather than a main test flight.
> +
> +
> +Email information headers
> +-------------------------
> +
> +Test report emails sent by osstest have some extra information in the
> +email headers, where applicable:
> +
> +X-Osstest-Versions-This:
> +    osstest=cc8b79ce9586d2b0fbddbd4260e876eab1d408d4
> +X-Osstest-Versions-That:
> +    osstest=280a18b2b2612174e473a1c1a137ddd47c49aab9
> +    ^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> +     tree     revision

Some description of what this and that mean might be useful for those in
the know? Specifically that that is the baseline.

Also, I think in real life several trees might be included?



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel