From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>,
pbs-devel@lists.proxmox.com
Subject: [pve-devel] applied: [PATCH proxmox-widget-toolkit 1/2] FileBrowser: allow downloading root folder and simplify code
Date: Tue, 13 Apr 2021 09:02:16 +0200 [thread overview]
Message-ID: <58c35939-5b03-6d98-f959-4f56e52942da@proxmox.com> (raw)
In-Reply-To: <20210412153252.22652-1-s.reiter@proxmox.com>
On 12.04.21 17:32, Stefan Reiter wrote:
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> ---
>
> Smoke tested by downloading an entire container archive as zip, extracting and
> checking the files. If there was a reason for this to be disabled let me know.
>
> Based on my previous series to move the FileBrowser to the widget toolkit:
> https://lists.proxmox.com/pipermail/pbs-devel/2021-April/002590.html
>
> Depends on the proxmox-backup patch to work correctly.
>
> src/window/FileBrowser.js | 18 +-----------------
> 1 file changed, 1 insertion(+), 17 deletions(-)
>
>
applied, thanks!
Added a actual config sections with comments for the widget specific params.
WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>,
pbs-devel@lists.proxmox.com
Subject: [pbs-devel] applied: [pve-devel] [PATCH proxmox-widget-toolkit 1/2] FileBrowser: allow downloading root folder and simplify code
Date: Tue, 13 Apr 2021 09:02:16 +0200 [thread overview]
Message-ID: <58c35939-5b03-6d98-f959-4f56e52942da@proxmox.com> (raw)
In-Reply-To: <20210412153252.22652-1-s.reiter@proxmox.com>
On 12.04.21 17:32, Stefan Reiter wrote:
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> ---
>
> Smoke tested by downloading an entire container archive as zip, extracting and
> checking the files. If there was a reason for this to be disabled let me know.
>
> Based on my previous series to move the FileBrowser to the widget toolkit:
> https://lists.proxmox.com/pipermail/pbs-devel/2021-April/002590.html
>
> Depends on the proxmox-backup patch to work correctly.
>
> src/window/FileBrowser.js | 18 +-----------------
> 1 file changed, 1 insertion(+), 17 deletions(-)
>
>
applied, thanks!
Added a actual config sections with comments for the widget specific params.
next prev parent reply other threads:[~2021-04-13 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 15:32 [pve-devel] " Stefan Reiter
2021-04-12 15:32 ` [pbs-devel] " Stefan Reiter
2021-04-12 15:32 ` [pve-devel] [PATCH proxmox-backup 2/2] api/datastore: allow pxar file download of entire archive Stefan Reiter
2021-04-12 15:32 ` [pbs-devel] " Stefan Reiter
2021-04-13 6:39 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-13 6:39 ` [pbs-devel] applied: " Thomas Lamprecht
2021-04-13 7:23 ` [pve-devel] " Dominik Csapak
2021-04-13 7:23 ` Dominik Csapak
2021-04-13 7:29 ` [pve-devel] " Thomas Lamprecht
2021-04-13 7:29 ` Thomas Lamprecht
2021-04-13 7:02 ` Thomas Lamprecht [this message]
2021-04-13 7:02 ` [pbs-devel] applied: [pve-devel] [PATCH proxmox-widget-toolkit 1/2] FileBrowser: allow downloading root folder and simplify code 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=58c35939-5b03-6d98-f959-4f56e52942da@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.reiter@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.