Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Eric Ren <zren@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 test project current status ANNOUNCEMENT
Date: Fri, 9 Oct 2015 13:12:07 +0800	[thread overview]
Message-ID: <20151009051207.GA11859@laptop.ha> (raw)

Hi all,

Now, we have already collected 55 patches into Mark's github repo[1]
since Mar 16, 2012.
[1] https://github.com/markfasheh/ocfs2-test

Thanks a lot for their contributors:
    Junxiao Bi: 23
    Jeff Liu: 11
    Tiger Yang: 12
    Goldwynr: 5
    Eric Ren: 3
    Gang He: 1

This patches below are dropped, need improved, or conflicted with
previous ones:

[PATCH 09/10] Trigger udev rescan to get volume label that mkfs made remotely.   -- relate to blkid.conf, needs improved
[PATCH 42/59] mmap-test: fix segment fault  -- needs improved
[PATCH 48/59] ocfs2-test: fix build error   -- conflicted, dropped
[PATCH 45/59] flock-test: disable posix lock test   -- needs improved
[PATCH 53/59] discontig: fix remote mount   -- conflicted, dropped
[PATCH 32/59] xattr-test: fix single test failed    -- conflicted, dropped
[PATCH 17/59] Splice: Fix conflict definition of splice(2) for splice tests.    -- conflicted, dropped
[PATCH 13/59] aio-stress: fix aio-stress Makefile to link pthread explicitly.   -- conflicted, dropped

There might be some incorrectness in my conclusion. For details, please
refer to ocfs2-test-devel mailist!

Test project is very important to ensure the quality of ocfs2. Welcome
more contributions from you! Let's make it better;-)

Thanks,
Eric

             reply	other threads:[~2015-10-09  5:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  5:12 Eric Ren [this message]
2015-10-09  5:36 ` [Ocfs2-devel] OCFS2 test project current status ANNOUNCEMENT Gang He
2015-10-09  6:09 ` Junxiao Bi
2015-10-09 16:10   ` [Ocfs2-devel] [Ocfs2-test-devel] " Srinivas Eeda
2015-10-10  8:21 ` [Ocfs2-devel] " eric

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=20151009051207.GA11859@laptop.ha \
    --to=zren@suse.com \
    --cc=ocfs2-devel@oss.oracle.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