From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: New Defects reported by Coverity Scan for ceph (fwd)
Date: Sat, 12 Apr 2014 10:26:05 +0200 [thread overview]
Message-ID: <5348F89D.3080407@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1404112105310.16913@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
I'll deal with the problems found in gf-complete: http://tracker.ceph.com/issues/8083
On 12/04/2014 06:06, Sage Weil wrote:
> Several new defects. This wasn't running for the last couple of weeks
> because the submodules didn't update on the test checkout.
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-04-12 8:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 4:06 New Defects reported by Coverity Scan for ceph (fwd) Sage Weil
2014-04-12 8:26 ` Loic Dachary [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 14:59 Sage Weil
2014-09-30 13:59 Sage Weil
2014-09-30 17:26 ` Loic Dachary
2014-09-30 17:36 ` Gregory Farnum
2014-09-30 17:38 ` Sage Weil
2014-09-30 17:41 ` Ric Wheeler
2014-09-25 15:02 Sage Weil
2014-09-25 15:27 ` John Spray
2014-09-16 21:44 Sage Weil
2014-08-23 16:04 Sage Weil
2014-07-11 3:39 Sage Weil
2014-06-20 14:46 Sage Weil
2014-06-07 16:12 Sage Weil
2014-06-08 8:38 ` Sebastien Ponce
2014-06-18 7:37 ` Sebastien Ponce
2014-06-06 15:54 Sage Weil
2014-05-30 13:54 Sage Weil
2014-05-20 16:16 Sage Weil
2014-05-10 16:03 Sage Weil
2014-04-22 15:26 Sage Weil
2014-03-03 22:23 Sage Weil
2014-03-03 22:53 ` John Spray
2014-03-04 0:53 ` Li Wang
2013-12-17 17:10 Sage Weil
2013-12-16 16:07 Sage Weil
2013-12-17 9:01 ` Ilya Dryomov
2013-08-21 4:09 Sage Weil
2013-07-25 20:31 Sage Weil
2013-07-19 18:04 Sage Weil
2013-06-19 19:36 Sage Weil
2013-06-19 21:03 ` Loic Dachary
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=5348F89D.3080407@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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