From: Matthias Heiserer <m.heiserer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Laurent GUERBY <laurent@guerby.net>
Subject: Re: [pve-devel] New API endpoint to manage snippets / bugzilla 2208 / updated patch but missing something, need help
Date: Mon, 11 Apr 2022 11:03:33 +0200 [thread overview]
Message-ID: <9881cc3c-e316-2f8d-2be4-cb36e3161045@proxmox.com> (raw)
In-Reply-To: <1649408819.6346.22.camel@guerby.net>
Hi,
please take a look at our developer documentation.
https://pve.proxmox.com/wiki/Developer_Documentation
Using `git format-patch` makes applying the changes a whole lot easier :)
As far as I can tell from a quick test, your changes seem to work.
Would you mind using `pvesh create` to test?
If it doesn't work there either, make sure to include the exact
command/code you used so people can try to reproduce the problem.
next prev parent reply other threads:[~2022-04-11 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 10:27 [pve-devel] New API endpoint to manage snippets Patryk Ściborek
2022-04-08 9:06 ` [pve-devel] New API endpoint to manage snippets / bugzilla 2208 / updated patch but missing something, need help Laurent GUERBY
2022-04-08 18:25 ` Laurent GUERBY
2022-04-11 9:03 ` Matthias Heiserer [this message]
2022-04-11 10:00 ` Laurent GUERBY
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=9881cc3c-e316-2f8d-2be4-cb36e3161045@proxmox.com \
--to=m.heiserer@proxmox.com \
--cc=laurent@guerby.net \
--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