From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Fabian Ebner <f.ebner@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] prune sim: correctly keep track of already included backups
Date: Tue, 15 Dec 2020 14:04:20 +0100 [thread overview]
Message-ID: <e855d723-2078-fa2a-5950-90859d54613d@proxmox.com> (raw)
In-Reply-To: <20201214150453.28946-1-f.ebner@proxmox.com>
On 14.12.20 16:04, Fabian Ebner wrote:
> This needs to happen in a separate loop, because some time intervals are not
> subsets of others, i.e. weeks and months. Previously, with a daily backup
> schedule, having:
> * a backup on Sun, 06 Dec 2020 kept by keep-daily
> * a backup on Sun, 29 Nov 2020 kept by keep-weekly
> would lead to the backup on Mon, 30 Nov 2020 to be selected for keep-monthly,
> because the iteration did not yet reach the backup on Sun, 29 Nov 2020 that
> would mark November as being covered.
>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> docs/prune-simulator/prune-simulator.js | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2020-12-15 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:04 [pbs-devel] " Fabian Ebner
2020-12-14 15:08 ` Fabian Ebner
2020-12-15 13:04 ` Thomas Lamprecht [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=e855d723-2078-fa2a-5950-90859d54613d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pbs-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox