From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: appendices/contributing/devbook-guide/
Date: Tue, 19 Mar 2019 20:25:54 +0000 (UTC) [thread overview]
Message-ID: <1553027130.a39f9d241fb906cc2c7442fe5318f9630dce54df.ulm@gentoo> (raw)
commit: a39f9d241fb906cc2c7442fe5318f9630dce54df
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 19 20:25:30 2019 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Mar 19 20:25:30 2019 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=a39f9d24
appendices/contributing/devbook-guide: Update all links to https.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
appendices/contributing/devbook-guide/text.xml | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/appendices/contributing/devbook-guide/text.xml b/appendices/contributing/devbook-guide/text.xml
index 564e29d..4563e46 100644
--- a/appendices/contributing/devbook-guide/text.xml
+++ b/appendices/contributing/devbook-guide/text.xml
@@ -58,7 +58,7 @@ using GuideXML.</i>
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
-<!-- See http://creativecommons.org/licenses/by-sa/3.0 -->
+<!-- See https://creativecommons.org/licenses/by-sa/3.0 -->
<license version="3.0"/>
<version><i>1</i></version>
@@ -111,7 +111,7 @@ required) that these tags appear before the content of the document.
<p>
Finally we have the <c><license version="3.0"/></c> tag, used to publish
-the document under the <uri link="http://creativecommons.org/licenses/by-sa/3.0/">Creative
+the document under the <uri link="https://creativecommons.org/licenses/by-sa/3.0/">Creative
Commons - Attribution / Share Alike</uri> license as required by the <uri
link="/proj/en/gdp/doc/doc-policy.xml">Documentation Policy</uri>. Historically,
the tag <c><license /></c> was used, which denoted the 2.5 version of the
@@ -183,7 +183,7 @@ an example <c><body></c> element:
<codesample lang="sgml"><!-- Example of a body element -->
<p>
This is a paragraph. <path>/etc/passwd</path> is a file.
-<uri>http://forums.gentoo.org</uri> is my favorite website.
+<uri>https://forums.gentoo.org</uri> is my favorite website.
Type <c>ls</c> if you feel like it. I <e>really</e> want to go to sleep now.
</p>
@@ -214,7 +214,7 @@ Now, here's how the <c><body></c> element above is rendered:
<p>
This is a paragraph. <path>/etc/passwd</path> is a file.
-<uri>http://forums.gentoo.org</uri> is my favorite web site.
+<uri>https://forums.gentoo.org</uri> is my favorite web site.
Type <c>ls</c> if you feel like it. I <e>really</e> want to go to sleep now.
</p>
@@ -322,13 +322,13 @@ Fill this section with the information about the use of
The <c><uri></c> tag is used to point to files/locations on the Internet.
It has two forms -- the first can be used when you want to have the actual URI
displayed in the body text, such as this link to
-<uri>http://forums.gentoo.org/</uri>. To create this link, I typed
-<c><uri>http://forums.gentoo.org/</uri></c>. The alternate form is
+<uri>https://forums.gentoo.org/</uri>. To create this link, I typed
+<c><uri>https://forums.gentoo.org/</uri></c>. The alternate form is
when you want to associate a URI with some other text -- for example, <uri
-link="http://forums.gentoo.org/">the Gentoo Forums</uri>. To create
-<e>this</e> link, I typed <c><uri link="http://forums.gentoo.org/">the
+link="https://forums.gentoo.org/">the Gentoo Forums</uri>. To create
+<e>this</e> link, I typed <c><uri link="https://forums.gentoo.org/">the
Gentoo Forums</uri></c>. You don't need to write
-<c>http://www.gentoo.org/</c> to link to other parts of the Gentoo web site.
+<c>https://www.gentoo.org/</c> to link to other parts of the Gentoo web site.
For instance, a link to the <uri link="/doc/en/">documentation main index</uri>
should be simply <c><uri link="/doc/en/index.xml">documentation main
index</uri></c>. You can even omit <c>index.xml</c> when you link to a
@@ -337,9 +337,9 @@ index</uri></c>. Leaving the trailing slash saves an extra HTTP request.
</p>
<p>
-Please avoid the <uri link="http://en.wikipedia.org/wiki/Click_here">click here
+Please avoid the <uri link="https://en.wikipedia.org/wiki/Click_here">click here
syndrome</uri> as recommended by the <uri
-link="http://www.w3.org/QA/Tips/noClickHere">W3C</uri>.
+link="https://www.w3.org/QA/Tips/noClickHere">W3C</uri>.
</p>
</body>
@@ -584,8 +584,8 @@ Code Listings should <e>always</e> have a <c>caption</c>.
<p>
Try to use <c><uri></c> with the <c>link</c> attribute as much as
-possible. In other words, the <uri link="http://forums.gentoo.org">Gentoo
-Forums</uri> is preferred over <uri>http://forums.gentoo.org</uri>.
+possible. In other words, the <uri link="https://forums.gentoo.org">Gentoo
+Forums</uri> is preferred over <uri>https://forums.gentoo.org</uri>.
</p>
</body>
next reply other threads:[~2019-03-19 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 20:25 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-29 9:28 [gentoo-commits] proj/devmanual:master commit in: appendices/contributing/devbook-guide/ Ulrich Müller
2019-12-09 21:39 Ulrich Müller
2019-12-09 21:39 Ulrich Müller
2019-12-26 21:36 Ulrich Müller
2019-12-26 21:36 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=1553027130.a39f9d241fb906cc2c7442fe5318f9630dce54df.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