From: Filip Schauer <f.schauer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH backup-qemu/vma-to-pbs 0/2] add support for notes and logs
Date: Wed, 10 Jul 2024 11:20:52 +0200 [thread overview]
Message-ID: <94aa3143-4248-45e2-8ad8-c625c0944e1e@proxmox.com> (raw)
In-Reply-To: <1720016624.v76n5kzczu.astroid@yuna.none>
Superseded by:
https://lists.proxmox.com/pipermail/pbs-devel/2024-July/010136.html
On 03/07/2024 16:24, Fabian Grünbichler wrote:
> On July 3, 2024 3:28 pm, Filip Schauer wrote:
>> On 03/07/2024 15:06, Fabian Grünbichler wrote:
>>>> proxmox-backup-qemu:
>>>>
>>>> Filip Schauer (1):
>>>> add support for notes
>>> I am not sure this is really warranted, especially since we don't want
>>> to keep using the proxmox-backup-qemu lib here in the long run anyway,
>>> but switch to a (to-be-extracted) pure Rust client directly..
>>>
>>> as a stop-gap measure, couldn't we just use `proxmox-backup-client` to
>>> set the notes?
>>
>> Yes, we could. The only downside being that we would have to open two
>> connections to the Proxmox Backup Server.
> yes, that's also how it works with vzdump :)
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2024-07-10 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:07 Filip Schauer
2024-05-27 13:07 ` [pbs-devel] [PATCH backup-qemu 1/2] add support for notes Filip Schauer
2024-05-27 13:07 ` [pbs-devel] [PATCH vma-to-pbs 2/2] add support for notes and logs Filip Schauer
2024-07-03 13:06 ` [pbs-devel] [PATCH backup-qemu/vma-to-pbs 0/2] " Fabian Grünbichler
2024-07-03 13:28 ` Filip Schauer
2024-07-03 14:24 ` Fabian Grünbichler
2024-07-10 9:20 ` Filip Schauer [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=94aa3143-4248-45e2-8ad8-c625c0944e1e@proxmox.com \
--to=f.schauer@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 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.