From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Bruce Wainer <brwainer@gmail.com>
Subject: Re: [pve-devel] [PATCH zsync 6/6] fix #3351: allow keeping a different number of snapshots on source and destination
Date: Tue, 25 May 2021 07:10:52 +0200 [thread overview]
Message-ID: <f88669b8-0275-0edf-da10-c9becda97613@proxmox.com> (raw)
In-Reply-To: <CAPEXuiyByQ0HeSmHb5C9ScLD-bDt62zKnXYqAJfSsOZG9rHY+A@mail.gmail.com>
On 24.05.21 18:00, Bruce Wainer wrote:
> Hello Fabian,
> Since this is a series of patches, could you provide the full pve-zsync
> file with all the patches? It would be easier for me to test it this way.
FYI: If you have git ready (`apt install git` else) it wouldn't be to hard to
apply multiple patches from a mail:
1. git clone git://git.proxmox.com/git/pve-zsync.git
2. save all patch-mails from 1/6 to 6/6 in a folder, e.g. /tmp/patches
3. git am /tmp/patches/*
next prev parent reply other threads:[~2021-05-25 5:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 12:59 [pve-devel] [PATCH-SERIES zsync] " Fabian Ebner
2021-05-11 12:59 ` [pve-devel] [PATCH zsync 1/6] param_to_job: handle --maxsnap 0 on creation Fabian Ebner
2021-05-11 12:59 ` [pve-devel] [PATCH zsync 2/6] usage: improve maxsnap description Fabian Ebner
2021-05-11 12:59 ` [pve-devel] [PATCH zsync 3/6] remove all old snapshots belonging to a job Fabian Ebner
2021-05-11 12:59 ` [pve-devel] [PATCH zsync 4/6] snapshot_get: make interface agnostic to source/dest Fabian Ebner
2021-05-11 12:59 ` [pve-devel] [PATCH zsync 5/6] snapshot_destroy: " Fabian Ebner
2021-05-11 12:59 ` [pve-devel] [PATCH zsync 6/6] fix #3351: allow keeping a different number of snapshots on source and destination Fabian Ebner
2021-05-24 16:00 ` Bruce Wainer
2021-05-25 5:10 ` Thomas Lamprecht [this message]
2021-05-25 12:02 ` [pve-devel] applied-series: [PATCH-SERIES zsync] " Thomas Lamprecht
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=f88669b8-0275-0edf-da10-c9becda97613@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=brwainer@gmail.com \
--cc=pve-devel@lists.proxmox.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.