From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH v2] sg-report-flight: Add a succcess/failure column header.
Date: Fri, 3 Oct 2014 13:42:44 +0100 [thread overview]
Message-ID: <1412340164.12695.6.camel@citrix.com> (raw)
In-Reply-To: <21550.34468.241195.152302@mariner.uk.xensource.com>
On Fri, 2014-10-03 at 12:21 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH v2] sg-report-flight: Add a succcess/failure column header."):
> > Personally I'd have made $cell_html include the "<td" and "</td>" in the
> > result, since both of the callers just paste it into that context
> > anyway, but up to you.
>
> In some versions these cells were <th>.
Ah, makes sense then.
prev parent reply other threads:[~2014-10-03 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 11:56 [PATCH OSSTEST] sg-report-flight: Add a succcess/failure column header Ian Campbell
2014-10-02 17:06 ` [OSSTEST PATCH v2] " Ian Jackson
2014-10-03 8:38 ` Ian Campbell
2014-10-03 11:21 ` Ian Jackson
2014-10-03 12:42 ` Ian Campbell [this message]
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=1412340164.12695.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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).