From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v5] mg-all-branch-statuses: Show how up to date each branch is
Date: Wed, 8 Jul 2015 15:31:27 +0100 [thread overview]
Message-ID: <1436365887.23508.53.camel@citrix.com> (raw)
In-Reply-To: <21917.13155.744337.802660@mariner.uk.xensource.com>
On Wed, 2015-07-08 at 15:27 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v5] mg-all-branch-statuses: Show how up to date each branch is"):
> > Using report_find_push_age_info allows us to provide counts of
> > attempts since the last baseline on current tip as well as the first
> > attempt of each of those.
> ...
> > +abs=$HOME/public_html/all-branch-statuses.txt
> > +( date ; echo ; bash -x ./mg-all-branch-statuses ) > $abs.new
> > +mv $abs.new $abs
>
> AFAICT all this does is leave the output in a file ? Wouldn't it be
> nice to post it ?
Apart from the date header it is no different to the "example output"
given after the commit log. Or did you mean for the script to post it to
the list?
The file will be exposed as
osstest.test-lab/~osstest/all-branch-statuses.txt. I could arrange for
it to end up on logs.test-lab as well if you like.
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Thanks.
next prev parent reply other threads:[~2015-07-08 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 14:21 [PATCH OSSTEST v5] mg-all-branch-statuses: Show how up to date each branch is Ian Campbell
2015-07-08 14:27 ` Ian Jackson
2015-07-08 14:31 ` Ian Campbell [this message]
2015-07-08 14:33 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436365887.23508.53.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.