public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Shyam Mani" <fox2mike@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: distcc.xml
Date: Tue,  4 Apr 2006 12:14:14 +0000	[thread overview]
Message-ID: <200604041214.k34CEFJK023137@robin.gentoo.org> (raw)

fox2mike    06/04/04 12:14:14

  Modified:             distcc.xml
  Log:
  Put in a patch given by Lisa Seelye <lisa@gentoo.org> to clarify the Troubleshooting section

Revision  Changes    Path
1.35                 xml/htdocs/doc/en/distcc.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml?rev=1.35&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml?rev=1.35&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/distcc.xml.diff?r1=1.34&r2=1.35&cvsroot=gentoo

Index: distcc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- distcc.xml	21 Feb 2006 16:50:58 -0000	1.34
+++ distcc.xml	4 Apr 2006 12:14:14 -0000	1.35
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.34 2006/02/21 16:50:58 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.35 2006/04/04 12:14:14 fox2mike Exp $ -->
 
 <guide link="/doc/en/distcc.xml">
 
@@ -33,8 +33,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.15</version>
-<date>2006-02-18</date>
+<version>1.16</version>
+<date>2006-04-04</date>
 
 <chapter>
 <title>Introduction</title>
@@ -338,14 +338,14 @@
 <chapter>
 <title>Troubleshooting</title>
 <section>
-<title>Mozilla and Xorg</title>
+<title>Some Packages Don't Use Distcc</title>
 <body>
 
 <p>
 As you emerge various packages, you'll notice that some of them aren't being
-distributed (and aren't being built in parallel).  This is because the
-developers of the Mozilla and Xorg-X11 ebuilds intentionally disable parallel
-building because it is known to cause problems.
+distributed (and aren't being built in parallel). This may happen because the
+package's Makefile doesn't support parallel operations or the maintainer of the
+ebuild has explicitly disabled parallel operations due to a known problem.
 </p>
 
 <p>



-- 
gentoo-doc-cvs@gentoo.org mailing list



             reply	other threads:[~2006-04-04 12:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 12:14 Shyam Mani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-07 20:57 [gentoo-doc-cvs] cvs commit: distcc.xml Jan Kundrat
2008-01-11  7:05 Joshua Saddler
2007-06-21 23:46 Lukasz Damentko
2006-12-24 17:54 Josh Saddler
2006-09-04 10:23 Josh Saddler
2006-02-21 16:50 Jan Kundrat
2006-02-18 23:21 Josh Saddler
2006-01-25  9:16 Xavier Neys

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=200604041214.k34CEFJK023137@robin.gentoo.org \
    --to=fox2mike@lark.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@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