public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Question about "btrfs send/receive"
Date: Tue, 23 Jun 2015 21:21:30 -0700	[thread overview]
Message-ID: <20150624042130.GV16468@merlins.org> (raw)
In-Reply-To: <558A26A5.4050105@cn.fujitsu.com>

On Wed, Jun 24, 2015 at 11:40:21AM +0800, Cao jin wrote:
> Hi Marc,
>     I can`t access /perso/btrfs/2014-03.html on that server. But I
> guess it has similar content as
> https://btrfs.wiki.kernel.org/index.php/Incremental_Backup ?
>     If so, I am afraid incremental backup not suitable for a API
> implementation in libguestfs.
>     Is the simplest form a usual condition people will use for
> subvolume backup? Is the simplest form make sense in daily life?
 
Argh, you're probably trying to connect from China. If so, my apologies,
after repeated abuse and attacks from too many Chinese netblocks and
netblocks owners who never replied to any Email or did anything to
address the issues reported, I was forced to block all of China.

You'll find a copy here:
https://web.archive.org/web/20150619002831/http://marc.merlins.org/perso/btrfs/2014-03.html
Scroll down to 	2014/03/22

Cheers,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

      reply	other threads:[~2015-06-24  4:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  7:15 Question about "btrfs send/receive" Cao jin
2015-06-24  3:24 ` Marc MERLIN
2015-06-24  3:40   ` Cao jin
2015-06-24  4:21     ` Marc MERLIN [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=20150624042130.GV16468@merlins.org \
    --to=marc@merlins.org \
    --cc=caoj.fnst@cn.fujitsu.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