public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/
Date: Sun,  5 Jun 2016 12:43:21 +0000 (UTC)	[thread overview]
Message-ID: <1465130486.2e6e1cfa6f8e9eaf422197a7cee7a2f76ad84bb1.gokturk@gentoo> (raw)

commit:     2e6e1cfa6f8e9eaf422197a7cee7a2f76ad84bb1
Author:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Sun Jun  5 12:41:26 2016 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Sun Jun  5 12:41:26 2016 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=2e6e1cfa

ebuild-writing/functions: fix a typo in a <uri> tag s/.//

 ebuild-writing/functions/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ebuild-writing/functions/text.xml b/ebuild-writing/functions/text.xml
index 23d68f0..325a9b4 100644
--- a/ebuild-writing/functions/text.xml
+++ b/ebuild-writing/functions/text.xml
@@ -42,7 +42,7 @@ Downloading a package's source happens before any of these phases, so
 <c>emerge --fetchonly</c> should perform all the network access you
 need (unless you're using live ebuilds).  Network access outside of
 this would not be cached locally (e.g. in <c>${DISTDIR}</c>, see
-<uri link="::ebuild-writing/variables#Predefined Read-Only Variables."/>),
+<uri link="::ebuild-writing/variables#Predefined Read-Only Variables"/>),
 which makes it hard to have reproducible builds (see
 <uri link="::ebuild-writing/functions/src_unpack/cvs-sources#Disadvantages of CVS Sources"/>).
 Avoid network access in any phase by using local files, extending


             reply	other threads:[~2016-06-05 12:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 12:43 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-18  5:10 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/ Sam James
2020-12-29 22:08 Göktürk Yüksek
2019-11-12 17:18 Göktürk Yüksek
2019-11-12 17:18 Göktürk Yüksek
2016-02-23  7:17 Ulrich Müller
2015-09-12 10:58 Markos Chandras
2014-10-18 17:35 Markos Chandras

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=1465130486.2e6e1cfa6f8e9eaf422197a7cee7a2f76ad84bb1.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