PERFORCE change 155419 for review
Rene Ladan
rene at FreeBSD.org
Mon Dec 29 15:32:57 UTC 2008
http://perforce.freebsd.org/chv.cgi?CH=155419
Change 155419 by rene at rene_self on 2008/12/29 15:32:52
Fix whitespace errors I introduced.
FreeBSD -> &os; on lines which changed anyway.
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#10 edit
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/Makefile#13 edit
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/book.sgml#8 edit
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/chapters.ent#8 edit
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#10 (text+ko) ====
@@ -1663,7 +1663,7 @@
<emphasis>not</emphasis> intended as a place for code reviews or a
replacement for the &a.arch; or the &a.audit;. In fact
using it as such hurts the FreeBSD Project as it gives a sense of a
- closed list where general decisions affecting all of the FreeBSD
+ closed list where general decisions affecting all of the FreeBSD
using community are made without being <quote>open</quote>.
Last, but not least <emphasis>never, never ever, email
the &a.developers; and CC:/BCC: another FreeBSD list</emphasis>.
@@ -2018,7 +2018,7 @@
predominantly in that area.</para>
<para>Other areas of FreeBSD fall under the control of
- someone who manages an overall category of FreeBSD
+ someone who manages an overall category of FreeBSD
evolution, such as internationalization or networking.
See <ulink
url="&url.base;/administration.html">
@@ -2195,7 +2195,7 @@
<para>Please note that this does not mean you should not try to
improve the software in question; you are still more than
welcome to do so. Ideally, you should submit your patches to
- the vendor. If your changes are &os;-specific, talk to the
+ the vendor. If your changes are FreeBSD-specific, talk to the
maintainer; they may be willing to apply them locally. But
whatever you do, do <emphasis>not</emphasis> commit there by
yourself!</para>
@@ -2209,7 +2209,7 @@
<sect2>
<title>Policy on Multiple Architectures</title>
- <para>FreeBSD has added several new architecture ports during recent
+ <para>&os; has added several new architecture ports during recent
release cycles and is truly no longer an &i386; centric operating
system. In an effort to make it easier to keep FreeBSD portable
across the platforms we support, core has developed the following
@@ -2404,16 +2404,16 @@
maintainer is expected to work with the platform maintainers
to refine these changes. Major new toolchain components are
allowed to break support for Tier 2 architectures if the
- FreeBSD-local changes have not been incorporated upstream. The
+ &os;-local changes have not been incorporated upstream. The
toolchain maintainers are expected to provide prompt review of
any proposed changes and cannot block, through their inaction,
- changes going into the tree. New features added to FreeBSD
+ changes going into the tree. New features added to FreeBSD
should be feasible to implement on these platforms, but an
implementation is not required before the feature may be added
to the FreeBSD source tree. New features that may be difficult
to implement on Tier 2 architectures should provide a means of
disabling them on those architectures. The implementation of
- a Tier 2 architecture may be committed to the main FreeBSD
+ a Tier 2 architecture may be committed to the main FreeBSD
tree as long as it does not interfere with production work on
Tier 1 platforms, or substantially with other Tier 2 platforms.
Before a Tier 2 platform can be added to the FreeBSD base
@@ -2436,12 +2436,12 @@
system, some external patches for the architecture for ports
must be available.</para>
- <para>Tier 2 architectures can be integrated into the FreeBSD
+ <para>Tier 2 architectures can be integrated into the FreeBSD
handbook. The basics for how to get a system running must be
documented, although not necessarily for every single board or
system a Tier 2 architecture supports. The supported hardware
list must exist and should be no more than a couple of months
- old. It should be integrated into the FreeBSD
+ old. It should be integrated into the FreeBSD
documentation.</para>
<para>Current Tier 2 platforms are ARM, PowerPC, ia64, Sparc64 and
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/Makefile#13 (text+ko) ====
@@ -3,7 +3,7 @@
# $FreeBSDnl: doc/nl_NL.ISO8859-1/books/handbook/Makefile,v 1.19 2006/01/03 21:17:07 siebrand Exp $
#
# %SOURCE% en_US.ISO8859-1/books/handbook/Makefile
-# %SRCID% 1.111
+# %SRCID% 1.112
#
# Bouw het Nederlandse FreeBSD Handboek.
#
@@ -241,7 +241,6 @@
SRCS+= printing/chapter.sgml
SRCS+= security/chapter.sgml
SRCS+= serialcomms/chapter.sgml
-SRCS+= updating/chapter.sgml
SRCS+= users/chapter.sgml
SRCS+= vinum/chapter.sgml
SRCS+= virtualization/chapter.sgml
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/book.sgml#8 (text+ko) ====
@@ -3,7 +3,7 @@
$FreeBSDnl: doc/nl_NL.ISO8859-1/books/handbook/book.sgml,v 1.33 2006/01/08 10:06:50 siebrand Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/book.sgml
- %SRCID% 1.173
+ %SRCID% 1.174
-->
@@ -54,7 +54,6 @@
<!ENTITY % chap.virtualization "IGNORE">
<!ENTITY % chap.filesystems "IGNORE">
<!ENTITY % chap.dtrace "IGNORE">
-<!ENTITY % chap.updating "IGNORE">
<!ENTITY % pgpkeys SYSTEM "../../../share/pgpkeys/pgpkeys.ent"> %pgpkeys;
]>
@@ -328,7 +327,6 @@
zetten.</para>
</partintro>
- <![ %chap.updating; [ &chap.updating; ]]>
<![ %chap.serialcomms; [ &chap.serialcomms; ]]>
<![ %chap.ppp-and-slip; [ &chap.ppp-and-slip; ]]>
<![ %chap.mail; [ &chap.mail; ]]>
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/chapters.ent#8 (text+ko) ====
@@ -10,7 +10,7 @@
$FreeBSDnl: doc/nl_NL.ISO8859-1/books/handbook/chapters.ent,v 1.3 2004/10/21 16:57:00 siebrand Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/chapters.ent
- %SRCID% 1.38
+ %SRCID% 1.39
-->
<!ENTITY chap.preface SYSTEM "preface/preface.sgml">
@@ -47,7 +47,6 @@
<!ENTITY chap.dtrace SYSTEM "dtrace/chapter.sgml">
<!-- Deel vier -->
-<!ENTITY chap.updating SYSTEM "updating/chapter.sgml">
<!ENTITY chap.serialcomms SYSTEM "serialcomms/chapter.sgml">
<!ENTITY chap.ppp-and-slip SYSTEM "ppp-and-slip/chapter.sgml">
<!ENTITY chap.mail SYSTEM "mail/chapter.sgml">
More information about the p4-projects
mailing list