From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 docs] sysadmin: add section 'Firmware Updates' and references
Date: Wed, 20 Sep 2023 15:26:01 +0200 [thread overview]
Message-ID: <ae3de1f8-1b14-4a43-9247-5f13a0bcc727@proxmox.com> (raw)
In-Reply-To: <ec0d5a21-d4f4-4f9b-8590-967705405562@proxmox.com>
Am 20/09/2023 um 11:59 schrieb Dominik Csapak:
> personally i would be cautious to include such deep links to vendor sites in our
> documentation, because they can be outdated fast and it becomes a catch-up game....
>
> No strong feelings though if the others are fine with it.
I normally make web.archive scrape it, and sometimes even use that link then
(otherwise it's just to have the option to switch to that link if even still
relevant when the original breaks)
https://web.archive.org/
Can you please do so and use those links instead and send a v2 with Dominik's
R-b tag already included?
next prev parent reply other threads:[~2023-09-20 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:21 Alexander Zeidler
2023-09-11 10:27 ` Alexander Zeidler
2023-09-20 9:59 ` Dominik Csapak
2023-09-20 13:26 ` Thomas Lamprecht [this message]
2023-09-21 13:17 ` [pve-devel] applied: " Thomas Lamprecht
2023-09-21 13:50 ` Thomas Lamprecht
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=ae3de1f8-1b14-4a43-9247-5f13a0bcc727@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.zeidler@proxmox.com \
--cc=pve-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