public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: back&forth send/receiving?
Date: Sat, 18 Feb 2023 09:57:04 +0300	[thread overview]
Message-ID: <f55d595a-e96c-b890-bc40-81f7d5d389d0@gmail.com> (raw)
In-Reply-To: <b492bb2878c839b2ea9cb8a9c94124062e29f42d.camel@scientia.org>

On 18.02.2023 03:29, Christoph Anton Mitterer wrote:
> On Fri, 2023-02-17 at 20:25 +0300, Andrei Borzenkov wrote:
>> So copy1 and copy2 are identical. This is not what you said earlier
>> (at
>> least, it is not how what you said earlier sounded).
> 
> Well that are based on the same master, but their most recent snapshot
> from that *may* be a different one.
> 

We are going in circles. To continue incremental chain on another copy 
after switching to a new master you need common base snapshot on the new 
master and the other copy. If such base snapshot exists, you can 
continue - starting with this base snapshot. If such base snapshot does 
not exist - you cannot.



      reply	other threads:[~2023-02-18  6:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 16:42 back&forth send/receiving? Christoph Anton Mitterer
2023-02-04  6:10 ` Andrei Borzenkov
2023-02-06  3:07   ` Christoph Anton Mitterer
2023-02-06  4:16     ` Andrei Borzenkov
2023-02-06  4:31       ` Christoph Anton Mitterer
2023-02-06  6:46         ` Andrei Borzenkov
2023-02-17 17:12           ` Christoph Anton Mitterer
2023-02-17 17:25             ` Andrei Borzenkov
2023-02-18  0:29               ` Christoph Anton Mitterer
2023-02-18  6:57                 ` Andrei Borzenkov [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=f55d595a-e96c-b890-bc40-81f7d5d389d0@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=calestyo@scientia.org \
    --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