public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: tools-reference/bash/
Date: Fri, 12 Mar 2021 22:03:13 +0000 (UTC)	[thread overview]
Message-ID: <1615586576.0f141508fdd8aef771d598357e78f9578da7325e.ulm@gentoo> (raw)

commit:     0f141508fdd8aef771d598357e78f9578da7325e
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 12 21:07:35 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Mar 12 22:02:56 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0f141508

tools-reference/bash: fix typo

Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 tools-reference/bash/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools-reference/bash/text.xml b/tools-reference/bash/text.xml
index 0583184..56608c4 100644
--- a/tools-reference/bash/text.xml
+++ b/tools-reference/bash/text.xml
@@ -779,7 +779,7 @@ output (<c>stdout</c>) as a string.
 
 <note>
 The <c>`command`</c> construct also does this, but should be avoided in
-favour of <c>$(command )</c> for clarity, ease of reading and nesting purposes.
+favour of <c>$(command)</c> for clarity, ease of reading and nesting purposes.
 </note>
 
 <codesample lang="ebuild">


             reply	other threads:[~2021-03-12 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 22:03 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-10 17:15 [gentoo-commits] proj/devmanual:master commit in: tools-reference/bash/ Ulrich Müller
2022-05-27  9:02 Ulrich Müller
2022-05-27  9:02 Ulrich Müller
2022-05-27  9:02 Ulrich Müller
2022-05-27  9:02 Ulrich Müller
2022-05-27  9:02 Ulrich Müller
2021-03-21  5:48 Ulrich Müller
2021-03-12 22:03 Ulrich Müller

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=1615586576.0f141508fdd8aef771d598357e78f9578da7325e.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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