From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 3/9] local-btrfs: unify casing for btrfs
Date: Wed, 6 Mar 2024 18:19:36 +0100 [thread overview]
Message-ID: <92590235-6171-4494-ae80-1f7fd520d3a9@proxmox.com> (raw)
In-Reply-To: <20240304132221.901327-4-c.heiss@proxmox.com>
Am 04/03/2024 um 14:22 schrieb Christoph Heiss:
> It's mostly spelled BTRFS anyway in our documentation (and also the
> official casing AFAICS), so align a few instances where it spelled
> lowercase.
official spelling is really not consistent and includes at least btrfs,
BTRFS and Btrfs – but having use it one casing here makes it slightly
better so fine by me.
>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> local-btrfs.adoc | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
>
applied, thanks!
next prev parent reply other threads:[~2024-03-06 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:22 [pve-devel] [PATCH docs 0/9] improve & unify installation(-related) documentation Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 1/9] gitignore: add package build outputs Christoph Heiss
2024-03-06 17:16 ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 2/9] asciidoc: introduce `pricing-url` variable, much like pmg-docs Christoph Heiss
2024-03-06 17:16 ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 3/9] local-btrfs: unify casing for btrfs Christoph Heiss
2024-03-06 17:19 ` Thomas Lamprecht [this message]
2024-03-04 13:22 ` [pve-devel] [PATCH docs 4/9] getting-help: forum: align wording with pmg-docs Christoph Heiss
2024-03-06 17:19 ` [pve-devel] applied: " Thomas Lamprecht
2024-03-04 13:22 ` [pve-devel] [PATCH docs 5/9] package-repos: " Christoph Heiss
2024-03-05 8:28 ` Gabriel Goller
2024-03-05 12:00 ` Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 6/9] installation: iso: improve & " Christoph Heiss
2024-03-05 8:38 ` Gabriel Goller
2024-03-05 12:05 ` Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 7/9] installation: lvm-options: " Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 8/9] installation: zfs-options: " Christoph Heiss
2024-03-04 13:22 ` [pve-devel] [PATCH docs 9/9] installation: iso: reflow location and password dialog screenshots Christoph Heiss
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=92590235-6171-4494-ae80-1f7fd520d3a9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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 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.