From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] docs: fix typos
Date: Thu, 25 Jul 2024 10:29:45 +0200 [thread overview]
Message-ID: <s8ofrrxyiva.fsf@proxmox.com> (raw)
In-Reply-To: <cede35e8-1476-46a1-9d67-cb48c0494602@proxmox.com> (Aaron Lauterer's message of "Mon, 22 Jul 2024 15:58:36 +0200")
Aaron Lauterer <a.lauterer@proxmox.com> writes:
> Thanks for this patch.
>
> A few things need to be changed in the actually commands/API/… definitions as we
> autogenerate the manual pages.
>
> This is true for any file with `*-synopsis` or `*-opts*` in its name.
>
> Please send a v2 without the synopsis and opts files. For the synopsis and opts
> files, find the source and fix it there.
V2 sent, thanks.
--
Maximiliano
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-25 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 13:03 Maximiliano Sandoval
2024-07-22 13:58 ` Aaron Lauterer
2024-07-25 8:29 ` Maximiliano Sandoval [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=s8ofrrxyiva.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=a.lauterer@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