From: junlion@tormail.org
To: linux-btrfs@vger.kernel.org
Cc: Jan Schmidt <list.btrfs@jan-o-sch.net>,
Alex Lyakas <alex.btrfs@zadarastorage.com>
Subject: Re: Incremental btrfs receive in opposite direction fails
Date: Wed, 2 Jan 2013 22:19:19 +0000 [thread overview]
Message-ID: <1TqWcc-0003FU-1J@internal.tormail.org> (raw)
In-Reply-To: <20130102205351.GA2242@localhost>
> # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> # !! Now we've made it look as if mp1/foo.1 was received from !!
> # !! mp2/foo.1 when actually it was the other way around. !!
> # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Better just ignore what I wrote there, it's not completely correct.
(Because we do not modify mp1/foo.1 but snapshot it to mp1/foo.1rw
and modify that one.)
prev parent reply other threads:[~2013-01-02 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 22:42 Incremental btrfs receive in opposite direction fails junlion
2012-12-29 13:00 ` Alex Lyakas
2012-12-30 6:40 ` junlion
2013-01-02 16:57 ` Jan Schmidt
2013-01-02 20:56 ` Jun Lion
[not found] ` <20130102205351.GA2242@localhost>
2013-01-02 22:19 ` junlion [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=1TqWcc-0003FU-1J@internal.tormail.org \
--to=junlion@tormail.org \
--cc=alex.btrfs@zadarastorage.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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;
as well as URLs for NNTP newsgroup(s).