All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: dsterba@suse.cz
Cc: Eric Sandeen <sandeen@redhat.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	Mark Fasheh <mfasheh@suse.de>
Subject: Re: btrfs-progs: re-add send-test
Date: Tue, 09 Apr 2013 19:09:11 +0200	[thread overview]
Message-ID: <51644B37.8060904@jan-o-sch.net> (raw)
In-Reply-To: <20130409122726.GH18193@twin.jikos.cz>

On 09.04.2013 14:27, David Sterba wrote:
> On Tue, Apr 09, 2013 at 08:37:12AM +0200, Jan Schmidt wrote:
>> > On 06.04.2013 20:30, Eric Sandeen wrote:
>>> > > From: Mark Fasheh <mfasheh@suse.de>
>>> > > 
>>> > > btrfs-progs: re-add send-test
>>> > > 
>>> > > send-test.c links against libbtrfs and uses the send functionality provided
>>> > > to decode and print a send stream to the console.
>> > 
>> > This looks pretty much like fardump from Arne's far repository:
> AFAICS, send-test uses the NO_FILE_DATA mode, and the implementation
> differes (it calls into btrfs_read_and_process_send_stream, unlike
> fardump that dumps the attributes as it finds them), but the goal of the
> utility seems to be the same.

Good point, we will have to add something like NO_FILE_DATA to the far
lib (and probably even the zfs sender) as well.

> [snip]
>
> Are you fine with keeping send-test in btrfsprogs until then? It's not
> built by default so nobody will probably rely on it so it could get
> replaced by fardump eventually.

I'm absolutely fine with that. To make really sure we're not breaking
anything as soon as we organize things differently, I suggest prepending

+	printf("Output format is known to be changed. Do not rely on it. You have been warned.\n");

or the like, but I don't insist on it :-)

-Jan

      reply	other threads:[~2013-04-09 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 18:30 btrfs-progs: re-add send-test Eric Sandeen
2013-04-09  6:37 ` Jan Schmidt
2013-04-09 12:27   ` David Sterba
2013-04-09 17:09     ` Jan Schmidt [this message]

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=51644B37.8060904@jan-o-sch.net \
    --to=list.btrfs@jan-o-sch.net \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mfasheh@suse.de \
    --cc=sandeen@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 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.