* send/receive questions
@ 2012-12-05 5:29 Ins
2012-12-05 22:06 ` james northrup
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Ins @ 2012-12-05 5:29 UTC (permalink / raw)
To: linux-btrfs
Hello all,
The implementation of send/receive is very cool.
But I wonder whether there are any plans to support these features
below or not,
1. support writable subvolume
2. can skip something to receive, for example,
(1) only receive those commands in range [1000, ..), skip the
before 1000
(2) only receive changes after some time, like recent 3 days.
3. can revert one receive
Just like the patch command does
4. support this scene,
When doing the receive process, if it suddently be stopped,
how to continue the receive process.
If 2 and 3 can be supported, 4 may be easy.
It's true there may be many errors if we skip something to receive.
--
Thanks.
-Rock
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: send/receive questions
2012-12-05 5:29 send/receive questions Ins
@ 2012-12-05 22:06 ` james northrup
[not found] ` <CAPkEcwhJ1HTDDxg63n==JHvJWkrSYKUszdv2LLWscog4UzAUWQ@mail.gmail.com>
2012-12-09 9:04 ` Alex Lyakas
2 siblings, 0 replies; 4+ messages in thread
From: james northrup @ 2012-12-05 22:06 UTC (permalink / raw)
To: Ins; +Cc: linux-btrfs
more important, when will the emacs sendrecv.el be ready?
On Tue, Dec 4, 2012 at 9:29 PM, Ins <insfocus@gmail.com> wrote:
> Hello all,
>
> The implementation of send/receive is very cool.
>
> But I wonder whether there are any plans to support these features
> below or not,
>
> 1. support writable subvolume
>
> 2. can skip something to receive, for example,
> (1) only receive those commands in range [1000, ..), skip the
> before 1000
> (2) only receive changes after some time, like recent 3 days.
>
> 3. can revert one receive
> Just like the patch command does
>
> 4. support this scene,
> When doing the receive process, if it suddently be stopped,
> how to continue the receive process.
>
> If 2 and 3 can be supported, 4 may be easy.
>
> It's true there may be many errors if we skip something to receive.
>
>
> --
> Thanks.
> -Rock
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: send/receive questions
[not found] ` <CAPkEcwhJ1HTDDxg63n==JHvJWkrSYKUszdv2LLWscog4UzAUWQ@mail.gmail.com>
@ 2012-12-06 1:42 ` Ins
0 siblings, 0 replies; 4+ messages in thread
From: Ins @ 2012-12-06 1:42 UTC (permalink / raw)
To: james northrup; +Cc: linux-btrfs
What the emacs sendrecv.el does?
2012/12/6 james northrup <northrup.james@gmail.com>:
> more important, when will the emacs sendrecv.el be ready?
>
>
> On Tue, Dec 4, 2012 at 9:29 PM, Ins <insfocus@gmail.com> wrote:
>>
>> Hello all,
>>
>> The implementation of send/receive is very cool.
>>
>> But I wonder whether there are any plans to support these features
>> below or not,
>>
>> 1. support writable subvolume
>>
>> 2. can skip something to receive, for example,
>> (1) only receive those commands in range [1000, ..), skip the
>> before 1000
>> (2) only receive changes after some time, like recent 3 days.
>>
>> 3. can revert one receive
>> Just like the patch command does
>>
>> 4. support this scene,
>> When doing the receive process, if it suddently be stopped,
>> how to continue the receive process.
>>
>> If 2 and 3 can be supported, 4 may be easy.
>>
>> It's true there may be many errors if we skip something to receive.
>>
>>
>> --
>> Thanks.
>> -Rock
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Thanks.
-Rock
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: send/receive questions
2012-12-05 5:29 send/receive questions Ins
2012-12-05 22:06 ` james northrup
[not found] ` <CAPkEcwhJ1HTDDxg63n==JHvJWkrSYKUszdv2LLWscog4UzAUWQ@mail.gmail.com>
@ 2012-12-09 9:04 ` Alex Lyakas
2 siblings, 0 replies; 4+ messages in thread
From: Alex Lyakas @ 2012-12-09 9:04 UTC (permalink / raw)
To: Ins; +Cc: linux-btrfs
Hi,
> 4. support this scene,
> When doing the receive process, if it suddently be stopped,
> how to continue the receive process.
I sent a proposal and a patch to implement this in
http://www.spinics.net/lists/linux-btrfs/msg19387.html. However, it is
not easy to make this patch accepted. Also, I found a bug in this
patch so please don't try it out.
Alex.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-12-09 9:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-05 5:29 send/receive questions Ins
2012-12-05 22:06 ` james northrup
[not found] ` <CAPkEcwhJ1HTDDxg63n==JHvJWkrSYKUszdv2LLWscog4UzAUWQ@mail.gmail.com>
2012-12-06 1:42 ` Ins
2012-12-09 9:04 ` Alex Lyakas
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).