All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	Koen De Wit <koen.de.wit@oracle.com>
Subject: Re: [PATCH] xfstests: btrfs/308: simple sparse copy testcase for btrfs
Date: Fri, 24 May 2013 09:39:25 +1000	[thread overview]
Message-ID: <20130523233925.GF24543@dastard> (raw)
In-Reply-To: <519E4590.4080309@redhat.com>

On Thu, May 23, 2013 at 11:36:32AM -0500, Eric Sandeen wrote:
> From: Koen De Wit <koen.de.wit@oracle.com>
> 
> # Tests file clone functionality of btrfs ("reflinks"):
> #   - Reflink a file
> #   - Reflink the reflinked file
> #   - Modify the original file
> #   - Modify the reflinked file
> 
> [sandeen: add helpers, make several mostly-cosmetic
>  changes to the original testcase]
> 
> Signed-off-by: Koen De Wit <koen.de.wit@oracle.com>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> 
> Originally submitted as test 297

FWIW, this will conflict with Josef's new btrfs/308 patch. You don't
have to use monatomically increasing numbers for the tests anymore
in the fileystem specifc test directories - you could make these
tests btrfs/00[1-4].... :)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Koen De Wit <koen.de.wit@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: btrfs/308: simple sparse copy testcase for btrfs
Date: Fri, 24 May 2013 09:39:25 +1000	[thread overview]
Message-ID: <20130523233925.GF24543@dastard> (raw)
In-Reply-To: <519E4590.4080309@redhat.com>

On Thu, May 23, 2013 at 11:36:32AM -0500, Eric Sandeen wrote:
> From: Koen De Wit <koen.de.wit@oracle.com>
> 
> # Tests file clone functionality of btrfs ("reflinks"):
> #   - Reflink a file
> #   - Reflink the reflinked file
> #   - Modify the original file
> #   - Modify the reflinked file
> 
> [sandeen: add helpers, make several mostly-cosmetic
>  changes to the original testcase]
> 
> Signed-off-by: Koen De Wit <koen.de.wit@oracle.com>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> 
> Originally submitted as test 297

FWIW, this will conflict with Josef's new btrfs/308 patch. You don't
have to use monatomically increasing numbers for the tests anymore
in the fileystem specifc test directories - you could make these
tests btrfs/00[1-4].... :)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-05-23 23:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 16:36 [PATCH] xfstests: btrfs/308: simple sparse copy testcase for btrfs Eric Sandeen
2013-05-23 16:36 ` Eric Sandeen
2013-05-23 23:39 ` Dave Chinner [this message]
2013-05-23 23:39   ` Dave Chinner
2013-05-24  3:09 ` Eryu Guan
2013-05-24  3:09   ` Eryu Guan
2013-05-24  4:21   ` Eric Sandeen
2013-05-24  4:21     ` Eric Sandeen
2013-05-24 17:34 ` [PATCH V2] xfstests: btrfs/306: " Eric Sandeen
2013-05-24 17:34   ` Eric Sandeen

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=20130523233925.GF24543@dastard \
    --to=david@fromorbit.com \
    --cc=koen.de.wit@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=xfs@oss.sgi.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 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.