From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH widget-toolkit v2] cbind: document cbind by adding a small summary and example
Date: Wed, 27 Oct 2021 11:22:57 +0200 [thread overview]
Message-ID: <181f8147-a0c9-2317-8f98-0498604de3d1@proxmox.com> (raw)
In-Reply-To: <20211025093144.2644693-1-d.csapak@proxmox.com>
On 25/10/2021 11:31, Dominik Csapak wrote:
> Explain the use-case, the difference to normal binds, and give an
> example that contains all features that can be used with explanations.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> changes from v1:
> * rewrite of textual introduction to include more details about use
> * remove part about double-bind, should be clear from the 'applied
> once' bit.
> * remove comments in the example in favor of textual explanation at the
> beginning
> * add info about recursion and workaround (+example)
>
> src/mixin/CBind.js | 96 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 96 insertions(+)
>
>
applied, thanks!
prev parent reply other threads:[~2021-10-27 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 9:31 [pve-devel] " Dominik Csapak
2021-10-27 9:22 ` 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=181f8147-a0c9-2317-8f98-0498604de3d1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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