From: Willem Jan Withagen <wjw@digiware.nl>
To: Matt Benjamin <mbenjamin@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Has rgw recently switched to deque usuage??
Date: Sun, 21 Feb 2016 11:46:38 +0100 [thread overview]
Message-ID: <56C9958E.5020008@digiware.nl> (raw)
In-Reply-To: <1135436239.44164632.1456013615024.JavaMail.zimbra@redhat.com>
On 21-2-2016 01:13, Matt Benjamin wrote:
> Hi Willem,
>
> That's good news, but massive header re-ordering sounds suspicious. Likely, there are just missing unix headers.
Overnight the build completed.
Now running gmake check.
If that gets to my normal level of PASSED of around 110 of 133 than I
commit the rgw changes and you can find that in my pull to comment about
and we take it from there.
--WjW
next prev parent reply other threads:[~2016-02-21 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 14:41 Has rgw recently switched to deque usuage?? Willem Jan Withagen
2016-02-20 21:33 ` Matt Benjamin
2016-02-20 22:15 ` Willem Jan Withagen
2016-02-21 0:13 ` Matt Benjamin
2016-02-21 0:49 ` Willem Jan Withagen
2016-02-21 10:46 ` Willem Jan Withagen [this message]
2016-02-21 11:00 ` Matt Benjamin
2016-02-21 13:18 ` Willem Jan Withagen
2016-02-22 15:12 ` RGW include modifications to compile with Clang Willem Jan Withagen
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=56C9958E.5020008@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=mbenjamin@redhat.com \
/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