From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [OSSTEST PATCH 3/5] Emails: Provide README.email and link to it
Date: Tue, 30 Jun 2015 15:29:14 +0100 [thread overview]
Message-ID: <1435674554.21469.197.camel@citrix.com> (raw)
In-Reply-To: <1435672148-6183-4-git-send-email-ian.jackson@eu.citrix.com>
On Tue, 2015-06-30 at 14:49 +0100, Ian Jackson wrote:
> Also link to README, from the email footer.
>
> I have tested that the link to README works right now. The link to
> README.email does not yet, of course, but it will start to work when
> osstest pushes this change to production.
>
> CC: Andrew Cooper <andrew.cooper3@citrix.com>
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
>
> squash! Provide README.email
pumpkin!
Acked-by: Ian Campbell <ian.campbell@citrix.com>
next prev parent reply other threads:[~2015-06-30 14:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 13:49 [OSSTEST PATCH 0/5] Email improvements Ian Jackson
2015-06-30 13:49 ` [OSSTEST PATCH 1/5] sg-report-flight: Use `bodyprint' and `bodyprintf' Ian Jackson
2015-06-30 14:22 ` Ian Campbell
2015-06-30 13:49 ` [OSSTEST PATCH 2/5] sg-report-flight: Make bodyprint[f] defer the output Ian Jackson
2015-06-30 14:23 ` Ian Campbell
2015-06-30 13:49 ` [OSSTEST PATCH 3/5] Emails: Provide README.email and link to it Ian Jackson
2015-06-30 14:29 ` Ian Campbell [this message]
2015-06-30 13:49 ` [OSSTEST PATCH 4/5] Emails: Provide X-Osstest-Versions-This and That headers Ian Jackson
2015-06-30 14:31 ` Ian Campbell
2015-06-30 14:42 ` Ian Jackson
2015-06-30 14:50 ` Ian Campbell
2015-06-30 15:13 ` Ian Jackson
2015-06-30 13:49 ` [OSSTEST PATCH 5/5] Emails: Provide X-Osstest-Failures Ian Jackson
2015-06-30 14:34 ` Ian Campbell
2015-06-30 14:21 ` [OSSTEST PATCH 0/5] Email improvements 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=1435674554.21469.197.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@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 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.