From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/layman:master commit in: doc/
Date: Sat, 20 Oct 2012 04:19:00 +0000 (UTC) [thread overview]
Message-ID: <1350519128.ae3d902f050ecd64bac1eab0a499e1bed8a20907.dol-sen@gentoo> (raw)
commit: ae3d902f050ecd64bac1eab0a499e1bed8a20907
Author: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 18 00:12:08 2012 +0000
Commit: Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Thu Oct 18 00:12:08 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/layman.git;a=commit;h=ae3d902f
missesd one make.conf.
---
doc/layman.8.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/layman.8.txt b/doc/layman.8.txt
index 758c14f..57705af 100644
--- a/doc/layman.8.txt
+++ b/doc/layman.8.txt
@@ -275,8 +275,8 @@ There exists only one such cache file and it will be overwritten
every time you run *layman*.
-HANDLING /ETC/MAKE.CONF
-~~~~~~~~~~~~~~~~~~~~~~~
+HANDLING /ETC/PORTAGE/MAKE.CONF
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Since *layman* is designed to automatically handle the inclusion of
overlays into your system it needs to be able to modify the
*PORTDIR_OVERLAY* variable in your '/etc/portage/make.conf' file.
next reply other threads:[~2012-10-20 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 4:19 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-28 0:02 [gentoo-commits] proj/layman:master commit in: doc/ Devan Franchini
2015-03-27 23:42 Devan Franchini
2015-02-08 17:25 Brian Dolbec
2014-06-16 3:37 [gentoo-commits] proj/layman:gsoc2014 " Brian Dolbec
2014-06-16 3:40 ` [gentoo-commits] proj/layman:master " Brian Dolbec
2012-10-20 20:55 Brian Dolbec
2011-09-18 0:45 Brian Dolbec
2011-08-20 17:06 Brian Dolbec
2011-07-23 6:45 Brian Dolbec
2011-02-08 3:36 Sebastian Pipping
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=1350519128.ae3d902f050ecd64bac1eab0a499e1bed8a20907.dol-sen@gentoo \
--to=brian.dolbec@gmail.com \
--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