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: general-concepts/dependencies/
Date: Wed, 27 Sep 2023 08:30:25 +0000 (UTC)	[thread overview]
Message-ID: <1695803373.a970eb2d03e0856beaac41786e9e27fb7376875a.ulm@gentoo> (raw)

commit:     a970eb2d03e0856beaac41786e9e27fb7376875a
Author:     Petr Vaněk <arkamar <AT> atlas <DOT> cz>
AuthorDate: Wed Sep 27 07:22:02 2023 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Sep 27 08:29:33 2023 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=a970eb2d

general-concepts/dependencies: use <c> tag for dev-util/ebuildtester

Signed-off-by: Petr Vaněk <arkamar <AT> atlas.cz>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 general-concepts/dependencies/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index aea0d7f..b041444 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -702,7 +702,7 @@ package:
   <dd>
     A sure-way to find missing dependencies is to test your ebuild in a
     deprived environment. Chroots, containers, virtual machines and
-    dev-util/ebuildtester can achieve this.
+    <c>dev-util/ebuildtester</c> can achieve this.
   </dd>
 </dl>
 


             reply	other threads:[~2023-09-27  8:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  8:30 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-28 19:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/ Ulrich Müller
2022-06-24  9:14 Ulrich Müller
2022-05-27  9:00 Ulrich Müller
2022-05-22  6:37 Joonas Niilola
2022-05-22  6:37 Joonas Niilola
2022-02-21  5:22 Sam James
2022-02-21  5:22 Sam James
2021-10-19  9:27 Mike Frysinger
2021-10-13 13:42 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-01-29  7:59 Ulrich Müller
2020-01-29  7:59 Ulrich Müller
2020-01-29  7:59 Ulrich Müller
2020-01-23  7:47 Ulrich Müller
2019-12-21  5:19 Ulrich Müller
2019-10-16 18:49 Göktürk Yüksek
2018-09-10 15:20 Mike Gilbert
2017-09-25  4:31 Göktürk Yüksek
2017-09-25  4:31 Göktürk Yüksek
2017-09-25  4:31 Göktürk Yüksek
2014-10-18 17:40 Markos Chandras
2013-07-29 21:53 Julian Ospald
2013-07-29 21:53 Julian Ospald
2011-02-17 21:08 Jeremy Olexa

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=1695803373.a970eb2d03e0856beaac41786e9e27fb7376875a.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