From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 1/2] docs: s/apt-get/apt due to interactive use
Date: Tue, 28 Nov 2023 14:47:41 +0100 [thread overview]
Message-ID: <6e8922da-1116-4c94-8b6b-dbf7148d1719@proxmox.com> (raw)
In-Reply-To: <20231128111147.78112-1-a.zeidler@proxmox.com>
Am 28/11/2023 um 12:11 schrieb Alexander Zeidler:
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
> docs/installation.rst | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
>
applied both patches, thanks!
Second one needed a three-way merge to apply though.
FWIW and a pre-existing thing: having the swappiness values explained
in the middle of ZFS docs make not much sense, that should get moved to
a non-FS specific section..
prev parent reply other threads:[~2023-11-28 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 11:11 [pbs-devel] " Alexander Zeidler
2023-11-28 11:11 ` [pbs-devel] [PATCH proxmox-backup 2/2] docs: fix formatting Alexander Zeidler
2023-11-28 13:47 ` 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=6e8922da-1116-4c94-8b6b-dbf7148d1719@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.zeidler@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