From: Dietmar Maurer <dietmar@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Bruce Wainer <brwainer@gmail.com>,
Wolfgang Link <w.link@proxmox.com>
Cc: PVE development discussion <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-zsync 0/1] Allow pve-zsync jobs to share dest
Date: Thu, 26 Nov 2020 06:06:05 +0100 (CET) [thread overview]
Message-ID: <478743729.685.1606367166698@webmail.proxmox.com> (raw)
In-Reply-To: <CAPEXuiwFvLa7uct_h_t9UPJpcPrC0jzvZVgNLbNfNRVvYxdDsw@mail.gmail.com>
> It has been 5 months since my patch has been applied, however the version
> for pve-zsync has not been incremented and this patch is not in the version
> presented by the repo. What needs to be done?
Ok, just bumped the version and created a new package. So this will be part
of the next release (soon) ...
next prev parent reply other threads:[~2020-11-26 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <817953729.92.1592826225983@webmail.proxmox.com>
[not found] ` <D1795812-455D-4EAB-A0DD-0C323B907863@brucewainer.com>
[not found] ` <1101863268.50.1592902077180@webmail.proxmox.com>
2020-11-25 22:12 ` Bruce Wainer
2020-11-26 5:06 ` Dietmar Maurer [this message]
2020-11-26 8:05 ` Bruce Wainer
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=478743729.685.1606367166698@webmail.proxmox.com \
--to=dietmar@proxmox.com \
--cc=brwainer@gmail.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-devel@pve.proxmox.com \
--cc=w.link@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox