From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH docs 0/3] extend documentation for change detection mode
Date: Thu, 21 Nov 2024 17:04:23 +0100 [thread overview]
Message-ID: <f5daa768-f9c0-4bfa-a196-a3ceab51b578@proxmox.com> (raw)
In-Reply-To: <20241118092435.81880-1-c.ebner@proxmox.com>
Am 18.11.24 um 10:24 schrieb Christian Ebner:
> Add sections explaining the change detection modes in more technical
> details and reference to this sections in the client usage section,
> which should cover more the how-to-use than the how-it-works.
>
> Christian Ebner (3):
> docs: explain the working principle of the change detection modes
> docs: reference technical change detection mode section for client
> docs: client: fix formatting by using double ticks
>
> docs/backup-client.rst | 38 +++++--------
> docs/technical-overview.rst | 108 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 123 insertions(+), 23 deletions(-)
>
applied series, thanks!
I took the liberty of transofrming Shannon's "sounds good to me" into a
Reviewed-by, holler at me if I should not do that anymore in the future.
_______________________________________________
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-11-21 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 9:24 [pbs-devel] " Christian Ebner
2024-11-18 9:24 ` [pbs-devel] [PATCH docs 1/3] docs: explain the working principle of the change detection modes Christian Ebner
2024-11-18 9:24 ` [pbs-devel] [PATCH docs 2/3] docs: reference technical change detection mode section for client Christian Ebner
2024-11-18 9:24 ` [pbs-devel] [PATCH docs 3/3] docs: client: fix formatting by using double ticks Christian Ebner
2024-11-18 15:04 ` Shannon Sterz
2024-11-21 16: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=f5daa768-f9c0-4bfa-a196-a3ceab51b578@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.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