From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:devbook-guide commit in: appendices/contributing/devbook-guide/
Date: Mon, 17 Apr 2017 23:23:50 +0000 (UTC) [thread overview]
Message-ID: <1492466220.b9c01143d3999b7ef38adccd285624d48576e6d2.gokturk@gentoo> (raw)
commit: b9c01143d3999b7ef38adccd285624d48576e6d2
Author: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 17 21:57:00 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Mon Apr 17 21:57:00 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=b9c01143
appendices/contributing/devbook-guide: chapter doesn't support id attribute
Remove the information on creating uri links to chapters using their
id attribute. This doesn't work in devmanual as expected.
appendices/contributing/devbook-guide/text.xml | 16 ----------------
1 file changed, 16 deletions(-)
diff --git a/appendices/contributing/devbook-guide/text.xml b/appendices/contributing/devbook-guide/text.xml
index 6ad3a5d..2ad0ad7 100644
--- a/appendices/contributing/devbook-guide/text.xml
+++ b/appendices/contributing/devbook-guide/text.xml
@@ -483,22 +483,6 @@ to <uri link="#doc_chap2_pre2">code listing 2 in chapter 2</uri>, type
<c><uri link="#doc_chap2_pre2">code listing 2.2</uri></c>.
</p>
-<p>
-However, some guides change often and using such "counting" can lead to broken
-links. In order to cope with this, you can define a name for a
-<c><chapter></c>, <c><section></c> or a <c><tr></c> by using
-the <c>id</c> attribute, and then point to that attribute, like this:
-</p>
-
-<pre caption="Using the id attribute">
-<chapter id="foo">
-<title>This is foo!</title>
-...
-<p>
-More information can be found in the <uri link="#foo">foo chapter</uri>
-</p>
-</pre>
-
</body>
</section>
<section>
next reply other threads:[~2017-04-17 23:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 23:23 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-23 14:54 [gentoo-commits] proj/devmanual:devbook-guide commit in: appendices/contributing/devbook-guide/ Ulrich Müller
2018-09-23 14:54 Ulrich Müller
2018-09-23 14:54 Ulrich Müller
2017-07-29 20:55 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-17 23:23 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
2017-04-12 21:24 Göktürk Yüksek
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=1492466220.b9c01143d3999b7ef38adccd285624d48576e6d2.gokturk@gentoo \
--to=gokturk@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