From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/
Date: Sun, 5 Nov 2023 16:48:42 +0000 (UTC) [thread overview]
Message-ID: <1699202869.ecc2c5953a5523ab3f4d9709066042c124bf40fc.ulm@gentoo> (raw)
commit: ecc2c5953a5523ab3f4d9709066042c124bf40fc
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 16 07:16:43 2022 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Nov 5 16:47:49 2023 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=ecc2c595
devbook-guide: Document the todo element
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
appendices/devbook-guide/text.xml | 29 ++++++++++++++++++++---------
1 file changed, 20 insertions(+), 9 deletions(-)
diff --git a/appendices/devbook-guide/text.xml b/appendices/devbook-guide/text.xml
index 484a230..5015f0b 100644
--- a/appendices/devbook-guide/text.xml
+++ b/appendices/devbook-guide/text.xml
@@ -178,6 +178,11 @@ This is important.
<warning>
This is a warning.
</warning>
+
+<todo>
+Text inside a <c>todo</c> element will appear in the
+<uri link="::appendices/todo-list/"/>.
+</todo>
</codesample>
<p>
@@ -212,6 +217,11 @@ This is important.
This is a warning.
</warning>
+<todo>
+Text inside a <c>todo</c> element will appear in the
+<uri link="::appendices/todo-list/"/>.
+</todo>
+
</body>
</subsection>
</section>
@@ -224,15 +234,16 @@ This is a warning.
We introduced a lot of new tags in the previous section <d/> here's what you
need to know. The <c><p></c> (paragraph), <c><pre></c>
(preformatted block), <c><codesample></c> (code block),
-<c><note></c>, <c><important></c> and <c><warning></c> tags
-all can contain one or more lines of text. Besides the <c><figure></c>,
-<c><table></c>, <c><ul></c>, <c><ol></c>
-and <c><dl></c> elements (which we'll cover in just a bit), these are the
-only tags that should appear immediately inside a <c><body></c> element.
-Another thing <d/> these tags <e>should not</e> be stacked <d/> in other words,
-don't put a <c><note></c> element inside a <c><p></c> element. As
-you might guess, the <c><pre></c> and <c><codesample></c> elements
-preserve their whitespace exactly, making them well-suited for code excerpts:
+<c><note></c>, <c><important></c>, <c><warning></c> and
+<c><todo></c> tags all can contain one or more lines of text.
+Besides the <c><figure></c>, <c><table></c>, <c><ul></c>,
+<c><ol></c> and <c><dl></c> elements (which we'll cover in just
+a bit), these are the only tags that should appear immediately inside a
+<c><body></c> element. Another thing <d/> these tags <e>should not</e>
+be stacked <d/> in other words, don't put a <c><note></c> element inside
+a <c><p></c> element. As you might guess, the <c><pre></c> and
+<c><codesample></c> elements preserve their whitespace exactly, making
+them well-suited for code excerpts:
</p>
<codesample lang="sgml"><!-- Named <pre> -->
next reply other threads:[~2023-11-05 16:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 16:48 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-31 18:59 [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/ Ulrich Müller
2024-10-25 11:21 Ulrich Müller
2024-05-08 5:57 Ulrich Müller
2023-11-05 16:45 Ulrich Müller
2023-10-05 20:29 Ulrich Müller
2022-02-16 18:56 Ulrich Müller
2021-07-31 17:59 Ulrich Müller
2021-03-19 19:23 Ulrich Müller
2021-03-19 19:23 Ulrich Müller
2021-03-19 19:22 Ulrich Müller
2021-03-12 19:32 Ulrich Müller
2021-03-11 11:24 Ulrich Müller
2020-12-14 19:35 Ulrich Müller
2020-08-21 16:53 Ulrich Müller
2020-03-06 16:30 Ulrich Müller
2020-03-06 16:30 Ulrich Müller
2020-03-01 12:32 Ulrich Müller
2020-02-22 21:27 Ulrich Müller
2020-01-28 5:55 Ulrich Müller
2020-01-16 18:50 Ulrich Müller
2020-01-15 22:36 Ulrich Müller
2020-01-15 22:14 Ulrich Müller
2020-01-15 21:30 Ulrich Müller
2020-01-15 21:30 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 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=1699202869.ecc2c5953a5523ab3f4d9709066042c124bf40fc.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