From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: Re: [ptxdist] [APPLIED] doc: use correct spelling for Git/GitHub instead of all uppercase
Date: Tue, 3 Jun 2025 12:38:50 +0200 [thread overview]
Message-ID: <20250603103850.1198226-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250520114620.166168-2-m.heidelberg@cab.de>
Thanks, applied as 28f4845ead5fd90acdfb445a3acc78158a72f142.
Michael
[sent from post-receive hook]
On Tue, 03 Jun 2025 12:38:49 +0200, Markus Heidelberg <m.heidelberg@cab.de> wrote:
> Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> Message-Id: <20250520114620.166168-2-m.heidelberg@cab.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/daily_work.inc b/doc/daily_work.inc
> index f16cd490c614..7071a0f1577b 100644
> --- a/doc/daily_work.inc
> +++ b/doc/daily_work.inc
> @@ -5,7 +5,7 @@ Using an External Kernel Source Tree
>
> This application note describes how to use an external kernel source
> tree within a PTXdist project. In this case the external kernel source
> -tree is managed by GIT.
> +tree is managed by Git.
>
> Cloning the Linux Kernel Source Tree
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> @@ -74,7 +74,7 @@ enter it, and:
> configuration**.
>
> - If no patches should be used on top of the selected kernel source
> - tree, we keep the **patch series file** entry empty. As GIT should
> + tree, we keep the **patch series file** entry empty. As Git should
> help us to create these patches for deployment, it should be kept
> empty on default in this first step.
>
> @@ -98,7 +98,7 @@ config file**).
> Work Flow
> ~~~~~~~~~
>
> -Now it's up to ourself working on the GIT based kernel source tree and
> +Now it's up to ourself working on the Git based kernel source tree and
> using PTXdist to include the kernel into the root filesystem.
>
> To configure the kernel source tree, we simply run:
> @@ -594,7 +594,7 @@ Setting-Up the Distributed Compiler
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> How to setup the distributed compiler can be found on the project’s
> -homepage at GITHUB:
> +homepage at GitHub:
>
> https://github.com/icecc/icecream.
>
> diff --git a/doc/titlepage.inc b/doc/titlepage.inc
> index 2422291e7ebd..af18127832c1 100644
> --- a/doc/titlepage.inc
> +++ b/doc/titlepage.inc
> @@ -41,7 +41,7 @@
> +49\,(0)51\,21\,/\,20\,69\,17\,--\,0 (Fon)\\
> +49\,(0)51\,21\,/\,20\,69\,17\,--\,55\,55 (Fax)\\[1ex]
> info@pengutronix.de\\[2.5ex]
> - {\footnotesize \copyright \, \number \year \ Pengutronix, Hildesheim -- GIT Rev.\ |ptxdistBSPRevision| \negthinspace}
> + {\footnotesize \copyright \, \number \year \ Pengutronix, Hildesheim -- Git Rev.\ |ptxdistBSPRevision| \negthinspace}
> \end{textblock}
>
> \end{titlepage}
next prev parent reply other threads:[~2025-06-03 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 11:43 [ptxdist] [PATCH 1/2] Fix superfluous/duplicated words, grammar and typos Markus Heidelberg via ptxdist
2025-05-20 11:43 ` [ptxdist] [PATCH 2/2] doc: use correct spelling for Git/GitHub instead of all uppercase Markus Heidelberg via ptxdist
2025-06-03 10:38 ` Michael Olbrich [this message]
2025-05-20 11:51 ` [ptxdist] [PATCH 1/2] Fix superfluous/duplicated words, grammar and typos Alexander Dahl via ptxdist
2025-06-03 10:38 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20250603103850.1198226-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=m.heidelberg@cab.de \
--cc=ptxdist@pengutronix.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