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 3/4] ms-queuedaemon: Add report-projection
Date: Thu, 17 Sep 2015 17:39:42 +0100 [thread overview]
Message-ID: <1442507982.18856.231.camel@citrix.com> (raw)
In-Reply-To: <22010.60241.637402.404335@mariner.uk.xensource.com>
On Thu, 2015-09-17 at 17:33 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST 3/4] ms-queuedaemon: Add report
> -projection"):
> > No semantic change. Eventually more tasks will be added which are
> > wanted in report-projection but not report-plan.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Which reminds me, I meant to ack the first 2 before posting.
> Though you might want to avoid the word `task'. How about `Eventually
> more work will be done ...' ?
Sure.
Ian.
next prev parent reply other threads:[~2015-09-17 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:07 [PATCH OSSTEST v4] ms-flights-summary: Produce an HTML report of all active flights Ian Campbell
2015-09-17 16:14 ` Ian Campbell
2015-09-17 16:14 ` [PATCH OSSTEST 1/4] ms-queuedaemon: report-plan: Use rename-into-place for data-*.final.pl Ian Campbell
2015-09-17 16:47 ` Ian Campbell
2015-09-17 16:14 ` [PATCH OSSTEST 2/4] ms-queuedaemon: Break out catching-internally Ian Campbell
2015-09-17 16:47 ` Ian Campbell
2015-09-17 16:14 ` [PATCH OSSTEST 3/4] ms-queuedaemon: Add report-projection Ian Campbell
2015-09-17 16:33 ` Ian Jackson
2015-09-17 16:39 ` Ian Campbell [this message]
2015-09-17 16:14 ` [PATCH OSSTEST 4/4] ms-queuedaemon: Call ms-flights-summary upon completed plan/projection Ian Campbell
2015-09-17 16:34 ` Ian Jackson
2015-09-18 9:02 ` [PATCH OSSTEST v4] ms-flights-summary: Produce an HTML report of all active flights Ian Campbell
2015-09-18 10:27 ` Ian Campbell
2015-09-18 11:14 ` Ian Campbell
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=1442507982.18856.231.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).