From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Christopher Li <sparse@chrisli.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: master branch testing
Date: Fri, 11 Aug 2017 00:51:48 +0200 [thread overview]
Message-ID: <CAExDi1ST9p2h+3JX=-a6rhBPCw18tAvQOPjprF53wzeprD+iaw@mail.gmail.com> (raw)
In-Reply-To: <eba87902-3115-2ae7-fee9-0f2c352af2f3@ramsayjones.plus.com>
On Thu, Aug 10, 2017 at 11:42 PM, Ramsay Jones
<ramsay@ramsayjones.plus.com> wrote:
> Hi Chris,
>
> I have tested the current master branch (@ commit 5b247b1) on
> Linux 32-bit (i686), Linux 64-bit (x86-64) and cygwin (x86-64)
> and have found no additional problems. (sparse test-suite and
> git master next and pu branches).
>
> Thanks!
It's us that must thank you.
So ... Thank you!
-- Luc
next prev parent reply other threads:[~2017-08-10 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 21:42 master branch testing Ramsay Jones
2017-08-10 22:51 ` Luc Van Oostenryck [this message]
2017-08-10 23:58 ` Christopher Li
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='CAExDi1ST9p2h+3JX=-a6rhBPCw18tAvQOPjprF53wzeprD+iaw@mail.gmail.com' \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.com \
--cc=sparse@chrisli.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).