From: Laurent Vivier <laurent@vivier.eu>
To: Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] docs: Replace HomeBrew -> Homebrew
Date: Tue, 26 Apr 2022 12:40:52 +0200 [thread overview]
Message-ID: <b0da537b-080c-79d5-5466-4967e10ac204@vivier.eu> (raw)
In-Reply-To: <20220422083403.1082924-1-sw@weilnetz.de>
Le 22/04/2022 à 10:34, Stefan Weil a écrit :
> The official spelling does not use camel case.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> docs/about/build-platforms.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/about/build-platforms.rst b/docs/about/build-platforms.rst
> index c29a4b8fe6..e9163ba556 100644
> --- a/docs/about/build-platforms.rst
> +++ b/docs/about/build-platforms.rst
> @@ -80,7 +80,7 @@ Ubuntu LTS. Other distros will be assumed to ship similar software versions.
> For FreeBSD and OpenBSD, decisions will be made based on the contents of the
> respective ports repository, while NetBSD will use the pkgsrc repository.
>
> -For macOS, `HomeBrew`_ will be used, although `MacPorts`_ is expected to carry
> +For macOS, `Homebrew`_ will be used, although `MacPorts`_ is expected to carry
> similar versions.
>
> Windows
> @@ -92,6 +92,6 @@ hosted on Linux (Debian/Fedora).
> The version of the Windows API that's currently targeted is Vista / Server
> 2008.
>
> -.. _HomeBrew: https://brew.sh/
> +.. _Homebrew: https://brew.sh/
> .. _MacPorts: https://www.macports.org/
> .. _Repology: https://repology.org/
Applied to my trivial-patches branch.
Thanks,
Laurent
prev parent reply other threads:[~2022-04-26 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 8:34 [PATCH] docs: Replace HomeBrew -> Homebrew Stefan Weil
2022-04-22 8:44 ` Bin Meng
2022-04-26 10:40 ` Laurent Vivier [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=b0da537b-080c-79d5-5466-4967e10ac204@vivier.eu \
--to=laurent@vivier.eu \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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;
as well as URLs for NNTP newsgroup(s).