public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: Re: [PATCH v2 0/4] btrfs-progs: fix clone from wrong subvolume
Date: Wed, 4 Sep 2019 13:35:39 -0700	[thread overview]
Message-ID: <20190904203539.GF7452@vader> (raw)
In-Reply-To: <cover.1563822638.git.osandov@fb.com>

On Mon, Jul 22, 2019 at 12:15:01PM -0700, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
> 
> This is v2 of [1]. Changes from v1:
> 
> - Split out removing commented-out code to new patch 1 and removed a
>   related comment block.
> - Made subvol_path const char * in patch 2.
> - Added test case as patch 4.
> - Fixed wrong signed-off-by.
> 
> Thanks,
> Omar
> 
> 1: https://lore.kernel.org/linux-btrfs/cover.1563600688.git.osandov@fb.com/T/#u
> 
> Omar Sandoval (4):
>   btrfs-progs: receive: remove commented out transid checks
>   btrfs-progs: receive: get rid of unnecessary strdup()
>   btrfs-progs: receive: don't lookup clone root for received subvolume
>   btrfs-progs: tests: add test for receiving clone from duplicate
>     subvolume
> 
>  cmds/receive.c                                | 50 ++++---------------
>  .../test.sh                                   | 34 +++++++++++++
>  2 files changed, 45 insertions(+), 39 deletions(-)
>  create mode 100755 tests/misc-tests/038-receive-clone-from-current-subvolume/test.sh

Ping. Looks like only patch 2 is in the devel branch.

  parent reply	other threads:[~2019-09-04 20:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 19:15 [PATCH v2 0/4] btrfs-progs: fix clone from wrong subvolume Omar Sandoval
2019-07-22 19:15 ` [PATCH v2 1/4] btrfs-progs: receive: remove commented out transid checks Omar Sandoval
2019-07-24 11:22   ` David Sterba
2019-07-24 12:10     ` Filipe Manana
2019-07-22 19:15 ` [PATCH v2 2/4] btrfs-progs: receive: get rid of unnecessary strdup() Omar Sandoval
2019-07-22 19:15 ` [PATCH v2 3/4] btrfs-progs: receive: don't lookup clone root for received subvolume Omar Sandoval
2019-07-23 11:19   ` Filipe Manana
2020-02-24 14:53     ` Filipe Manana
2020-03-11  8:03       ` Omar Sandoval
2019-07-22 19:15 ` [PATCH v2 4/4] btrfs-progs: tests: add test for receiving clone from duplicate subvolume Omar Sandoval
2019-07-23 11:21   ` Filipe Manana
2019-09-04 20:35 ` Omar Sandoval [this message]
2019-10-10  7:06   ` [PATCH v2 0/4] btrfs-progs: fix clone from wrong subvolume Qu Wenruo

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=20190904203539.GF7452@vader \
    --to=osandov@osandov.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.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