public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: roberto.foglietta@gmail.com
To: isar-users@googlegroups.com
Cc: roberto.foglietta@gmail.com
Subject: [PATCH] Fixed 2 typos in RECIPE-API-CHANGELOG.md
Date: Tue, 06 Dec 2022 20:56:07 +0000	[thread overview]
Message-ID: <4uil8nqdd7i6.7XHbwuT_-yKUu7QgXrnCjQ2@16F0H.trk.elasticemail.com> (raw)

From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>

bugfix, typos, documentation - commit 87d31ee add some text to the
RECIPE-API-CHANGELOG.md but two words were mispelled, this fixes.

Fixes: 87d31ee ("add interface to passthrough env vars to sbuild")

Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
---
 RECIPE-API-CHANGELOG.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index 1b8efa5..0bb8338 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -436,8 +436,8 @@ specific bitbake variables as environment variables into the sbuild environment.
 The motivation behind it is to allow the use of external mirrors for programming languages with builtin
 package managers (like rust and go). By that, the variables are also excluded from the bitbake signatures.
 This helps in areas where default mirrors can either not be reached or provide only little throughput.
-Please note, the forwarded variables do not have to exist. While they are not forwared in case they do not
+Please note, the forwarded variables do not have to exist. While they are not forwarded in case they do not
 exist, empty variables are forwarded.
 
-**Note about reproducability**: the forwarded variables must not have any influence on the generated package.
+**Note about reproducibility**: the forwarded variables must not have any influence on the generated package.
 This mechanism must also not be used to inject build configurations. For these cases, templates should be used.
-- 
2.34.1


https://16F0H.trk.elasticemail.com/tracking/unsubscribe?d=9CW0B5Ng7nUYkLrs1lYZx1H6UbG-UpSyzvay_N-rFlFY-ILFVBC_5Ti3xaBKcQB6JQotDszQGyPL6zLEFY3ScOklo2XsameoU9pSlQf_yJl80

             reply	other threads:[~2022-12-07  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 20:56 roberto.foglietta [this message]
2022-12-14  7:24 ` Anton Mikanovich
  -- strict thread matches above, loose matches on Subject: below --
2022-12-06 15:18 roberto.foglietta

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=4uil8nqdd7i6.7XHbwuT_-yKUu7QgXrnCjQ2@16F0H.trk.elasticemail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.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